You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
I can verify that right now the AutoScalingGroup resource filtering is not granular enough by simply running the aws-nuke in a dry run mode. I get an output similar to the following one:
Has it been planned to include ASG resources for tag filtering as removing EC2 instances is fine but when keeping the ASG up and running new EC2s are spun up?
Thanks for your reply.
The text was updated successfully, but these errors were encountered:
Adding tags to various resources is in the backlog.
Please see the copy of the notice from the README about the deprecation of this project. Sven was kind enough to grant me access to help triage and close issues and pull requests that have already been addressed in the actively maintained fork. Some additional information is located in the welcome issue for more information.
Caution
This repository for aws-nuke is no longer being actively maintained. We recommend users to switch to the actively maintained fork of this project at ekristen/aws-nuke.
We appreciate all the support and contributions we've received throughout the life of this project. We believe that the fork will continue to provide the functionality and support that you have come to expect from aws-nuke.
Please note that this deprecation means we will not be addressing issues, accepting pull requests, or making future releases from this repository.
Thank you for your understanding and support.
I can verify that right now the AutoScalingGroup resource filtering is not granular enough by simply running the aws-nuke in a dry run mode. I get an output similar to the following one:
I can also check (in
v2.15.0
tag) that the following resources support tag matching:An example of the EC2Instance resource when matched for a removal is:
Has it been planned to include ASG resources for tag filtering as removing EC2 instances is fine but when keeping the ASG up and running new EC2s are spun up?
Thanks for your reply.
The text was updated successfully, but these errors were encountered: