Adding support for non-dedicated accounts about cloud-nuke HOT 4 CLOSED

This is not currently supported. Adding support for nuking resources with specific tags (for resources that support tags) makes sense, and a PR for that is welcome.

As for supporting nuking resources with specific IDs, that seems like a more esoteric use case. cloud-nuke is not a Terraform-specific tool, so I'm not a fan of building something into it to track IDs specific to Terraform functionality. Moreover, I'm not certain the approach would work in the general case. For example, to delete some resources, you must first delete all dependent resources: e.g., to delete a VPC, you must remove subnets; to remove subnets, you must remove attached security groups; and so on. So if you passed in the ID of just a VPC, would we automatically clean up the attached subnets and security groups, or only if you passed in the IDs for ALL of those? The former goes against the "delete only these IDs" concept, but the latter seems practically very hard to do, and unlikely to be used.

from cloud-nuke.

@brikis98 - Those are great points regarding the resource ID list, and I have to agree with you that the dependency-hierarchy problem would be a significant challenge.

Per your feedback, I may look deeper into adding the tag-filter option (for those resources that support tags) - unless of course someone else picks this up first 😄.

from cloud-nuke.

I noticed that tag-based exclusions are now becoming a thing (#103) - perhaps this would ease the way for tag-filtering as well... (?)

from cloud-nuke.

FYI - I've kicked off a PR to hopefully start to making progress on this: #109

Feedback and contributions welcome. :)

from cloud-nuke.