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
Right now, you will notice that we have separate routes for awsNuke and awsDefaults:
awsDefaults: nuking default VPCs
awsNuke: nuking other resources
However, there seems to be quite a lot of changes we can merge and streamline.
ec2.go file currently contains nuking operations for a lot of resources (e.g., internet gateway, subnet, route tables). Let's separate it out to individual resources.
we support functionality on individual resources to support nuking default vs. non-default resources
we make changes in awsDefaults to follow similar logic as awsNuke to nuke default resources.
we deprecate awsDefaults and create a parameter or config in awsNuke to target default resources.
The text was updated successfully, but these errors were encountered:
Context/Background
Right now, you will notice that we have separate routes for
awsNuke
andawsDefaults
:However, there seems to be quite a lot of changes we can merge and streamline.
ec2.go
file currently contains nuking operations for a lot of resources (e.g., internet gateway, subnet, route tables). Let's separate it out to individual resources.awsDefaults
to follow similar logic asawsNuke
to nuke default resources.awsDefaults
and create a parameter or config inawsNuke
to target default resources.The text was updated successfully, but these errors were encountered: