Should duffle run require a claim name on stateless actions?

[itowlson]

duffle run currently always requires a claim name (installation name).

However, the CNAB spec for the actions section (https://github.com/deislabs/cnab-spec/blob/master/101-bundle-json.md#custom-actions) says:

"stateless: The action does not act on a claim, and does not require credentials. This is useful for exposing dry-run actions, printing documentation, etc." (emphasis added)

Should the claim name be optional in duffle run if the action is stateless? For example, how should the user perform a "dry run" custom action if they have never installed the bundle?

[glyn]

Makes sense to me. Note that the spec also says:

Stateless actions can be invoked on a non-existing installation.

which I think is ambiguous. It could mean that an existing installation need not be supplied or that the installation name can be one that doesn't exist. I think the former makes more sense.

[itowlson]

I wonder if the spec is leaving open the possibility of a speculative "print a dry run of what would happen if I supplied this installation name" action. But I agree it seems confusing, and could make implementations more complicated.

I have raised issue cnabio/cnab-spec#252.