Closed rmsilva1973 closed 8 months ago
@rmsilva1973 Thanks for reporting this. We have added this to our backlog.
Looks like a duplicate of https://github.com/aws-solutions/aws-control-tower-customizations/issues/24
This is now supported in version 2.5.0
Describe the bug When we remove a stackset entirely from the manifest.yaml it doesn't get deleted by the pipeline
To Reproduce
(On our environment, we have several stacksets on manifest.yaml. Perhaps creating at least two different stacksets and removing one of them is a more certain way to reproduce)
Expected behavior Stackset should be deleted (and stack instances removed from all OUs/accounts) when it's entry is removed from manifest.yaml
Please complete the following information about the solution:
To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0089) - customizations-for-aws-control-tower Solution. Version: v1.0.0". You can also find the version from releases