Simplify CLI

[jamesroutley]

Full change list:

Current:                  Proposed:
continue-update-rollback  [unchanged]
create-change-set         [unchanged]
create-stack              create
delete-change-set         [unchanged]
delete-env                delete -r
delete-stack              delete
describe-change-set       [unchanged]
describe-env              [unchanged] (maybe it would be working adding a describe-stack command for symmetry)
describe-env-resources    describe-resources -r
describe-stack-outputs    describe-outputs
describe-stack-resources  describe-resources
execute-change-set        [unchanged]
generate-template         [unchanged]
get-stack-policy          get-policy
launch-env                launch -r
launch-stack              launch
list-change-sets          [unchanged]
lock-stack                lock
set-stack-policy          set-policy
unlock-stack              unlock
update-stack              update
update-stack-cs           update-cs (maybe implement this as a flag: update -cs)
validate-template         [unchanged]

Implementation

Rename CLI commands.

Pros

• The -r/--recursive syntax is more in keeping with Unix standards (e.g. cp, mv, grep)
• Commands are less verbose

Cons

• The original reason for having separate commands for building stacks and environments was to avoid users accidentally deleting whole environments. This would be mitigated by proposal 01.

[theseanything]

Just brainstorming ideas - this is a possible "aws cli"-esk structure of sceptre

Proposed:                 Current:
stack create              create-stack
stack update              update-stack
stack update -c           update-stack-cs
stack delete              delete-stack
stack delete -r           delete-env
stack launch              launch-stack
stack launch -r           launch-env
stack status              describe-stack
stack status -r           describe-env
stack rollback            continue-update-rollback
stack describe-outputs    describe-stack-outputs
stack describe-resources  describe-stack-resouces
change-set create         create-change-set
change-set delete         delete-change-set
change-set execute        execute-change-set
change-set list           list-change-sets
template validate         validate-template
template generate         generate-template
policy lock               lock-stack
policy unlock             unlock-stack
policy get                get-stack-policy
policy set                set-stack-policy

Although I like just having the command at the start like suggest in the initial comment. However not as neat due to the sets of change-set and template commands and continue-rollback.

I'm less bothered with keeping to strict unix standards as modern cli's have moved on from that (e.g. k8, docker, npm etc) and not sure what we benefit from it.

How about status instead of describe-env or possibly describe-stack?

[jamesroutley]

Oh yeah, that's cool - I like the way things are organised. Issues:

• Stack is an AWS word isn't it? - if we also support Azure would it be better to avoid that word?
• We remove the word "stack" from some of the commands even though those commands still fundamentally deal with stacks. The one of the arguments provided to those commands would still need to be a stack name.