-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some AWS Control Tower Resources Being Deleted W/ Updated Community Config #466
Comments
Any filter where you do not specify a property it defaults to the "stringer" which various resource to resource but for example it would be subnet-xxxxxxxxxx and so none of your filters will actually match therefore it is triggered for removal. |
So in this case the global section wouldn't filter out the subnets? What should I update to filter them? (And should the community preset be updated to include this?) |
All filters global or not have to be tied to a property if a property isn't given it uses the stringer property. There is no concept of a global property filter at this time. So in this case you want a tag. |
Understood and thank you. Happy to add this to the community preset as well. For anyone who finds this in the interim, I am adding:
|
Version:
3.29.1
Platform:
Aarch64
Example of the config working as expected:
Example of config working unexpectedly:
What is most strange is that there looks to be overlap between the config working as expected vs unexpected. In other words, the StackSet
AWSControlTowerBP-VPC-ACCOUNT-FACTORY-V1-d28321d4-eb6f
is filtered out in some cases (expected) but also deleted in others (unexpected).Here's the section of our config I am using for this:
Does the community preset/my config need to be updated?
The text was updated successfully, but these errors were encountered: