CfCT does not create SSM Parameter for successful StackSet resource if it fails on deploying the next StackSet

[suankan]

trafficstars

Describe the bug In case if CfCT pipeline fails to deploy some StackSet, then previously succeeded StackSet in the manifest does not create SSM Parameters according to its export_outputs section.

To Reproduce

• Create manifest with two StackSet resources.
• Include export_outputs section into the 1st manifest resource with CF Output.
• Make an intentional mistake in the 2nd manifest resource spec.

Expected behavior SSM Parameter from the 1st manifest resource should be created even if CfCT pipeline fails on the 2nd resource

Please complete the following information about the solution:

• [x] Version: v2.4.0
• [x] Region: ap-southeast-2
• [No] Was the solution modified from the version published on this repository?
• [N/A] If the answer to the previous question was yes, are the changes available on GitHub?
• [No] Have you checked your service quotas for the sevices this solution uses?
• [No] Were there any errors in the CloudWatch Logs?
  • I checked the CodeBuild Logs and didn't find any indication that CfCT even attempted to create such SSM Parameter.

[stumins]

Thanks for the report @suankan - I've added this to our backlog for review