The Customizations for AWS Control Tower solution combines AWS Control Tower and other highly-available, trusted AWS services to help customers more quickly set up a secure, multi-account AWS environment using AWS best practices.
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.
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
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: