Logging of missing parameters when using change-set's

[stevemac007]

We are using the change-set feature to help diff the impact of our cloudformation changes, and it is working really well. We have just run into an edge condition when we add new parameters to our stack.

The root cause is operator error, but stackup could help narrow down the issue with better logging.

When using the stack up command with missing parameters we see:

$ stackup db-dev-steve up -t cloudformation/db/master-stack.json -p parameters/db/common-params.json -o Environment=dev-steve
ERROR: ParameterValue for ParameterKey Account is required

But doing this via change-set create it doesn't say which parameter is in error.

$ stackup db-dev-steve change-set create -t cloudformation/db/master-stack.json -p parameters/db/common-params.json -o Environment=dev-steve
ERROR: Cannot specify UsePreviousValue on Parameters when ChangeSetType is CREATE

Would be great if the change-set create could output which parameter is in error.

[tigris]

Thanks for the detailed report @stevemac007 ! We'll check it out.