stack-create fails when multiple capabilities are required

[andrewlorien]

the --capabilities option only finds the first capability.
stack-create pgis-prod-Cloudwatch2S3 cloudformation/CloudWatch2S3.template cloudformation/parameters/prod/prod-CloudWatch2S3.json --capabilities=CAPABILITY_IAM CAPABILITY_AUTO_EXPAND

pull request coming soon.

[andrewlorien]

I agree with the suggestion at #146 that the capabilities syntax could be more intuitive. How about i just parse the end of the commandline for any legal capabilities. That way it's still backward compatible with anybody using --capabilities=CAPABILITY_IAM .

[mbailey]

Side note: One issue I have with the capabilities IAM is that I forget the syntax I need to use it.

I think the most beautiful behaviour would be to prompt the user with required options if they are omitted and get confirmation before running the updated command

[mbailey]

I agree with the suggestion at #146 that the capabilities syntax could be more intuitive. How about i just parse the end of the commandline for any legal capabilities. That way it's still backward compatible with anybody using --capabilities=CAPABILITY_IAM .

I think that sounds like a good solution and would be easy to add to shell completion.

Perhaps we could pause all arguments (rather than just at end) for any capabilities, and enable them if they are present?

[andrewlorien]

Side note: One issue I have with the capabilities IAM is that I forget the syntax I need to use it.

I think the most beautiful behaviour would be to prompt the user with required options if they are omitted and get confirmation before running the updated command

Any example of a confirmation-with-details already in bash-my-aws? I'd like to be consistent... otherwise i'll start with the yes/no in stack-delete