Changing ssm_parameter name: isnt actioned if no stack updates are required

[adamcousins]

When i modify or add the ssm_parameters: key for outputs of the stack_sets and there is no action required on the stack set, the pipeline will fail upon the next stackset which is expecting the ssm paramater to exist.

Is there a way to force ssm_parameters to be always processed even if there is no stack changes?

[groverlalit]

@adamcousins Thanks for bring this to our attention. We will add this as a feature request to our backlog. There is not manual way to trigger the SM execution. You can either update the SM event and execute the SM manually (for the stack set that adds the SSM parameter key/value) or you can update the SSM parameter store with the key and value. The second stack set that use the SSM key/value should read it in the next execution.