Consider making change set actions more verbose

[m1keil]

I just noticed that the delete option is shared between both the general stack destruction and change set deletion. While it makes CLI footprint smaller, it does introduce a subtle risk.

For example, right now to delete a change set, you need to do something like:

sceptre delete --yes PATH MYCHANGESETNAME

However it's relatively trivial to just fat finger and type

sceptre delete --yes PATH

instead. It is also becomes almost trivial to mess that up with bash scripting.

I suggest to add an explicit flag to the create/delete command so that changeset operations cannot be mixed up with regular stack operations:

sceptre delete [OPTIONS] PATH [--Change CHANGE_SET_NAME]

So if user explicitly type something like

sceptre delete --yes PATH --Change

it will error instead of destroying the entire stack.

[ngfgrant]

Hey @m1keil

I can see where you are coming from here. I think we keep it the same for v2 as it would be a breaking change. but something to consider for v3.