Feature Request: Exclude Resources by Tag Existence

[ErezWeiss]

Feature Request: Exclude Resources by Tag Existence in Cloud Nuke

Current Behavior:
Cloud Nuke currently supports excluding resources based on a specified key only if its value is "true".

Feature Request:
Add support for excluding resources based on the existence of a tag key, regardless of its value.

Use Case:
For example, if a resource has the tag Component: rds, I would like to exclude it by specifying isTagExist: Component. This ensures that all resources with the key Component (regardless of its value) are excluded from nuking.

Proposed Solution:
Introduce a new parameter isTagExist that accepts a tag key. If the specified key exists on a resource, the resource will be excluded.

Benefits:

• Provides more flexibility for users to manage exclusions.
• Simplifies scenarios where values of tags are dynamic or irrelevant.

Example Configuration:

excludeTags:
  isTagExist: Component

Would exclude any resource with the tag Component present, such as:

• Component: rds
• Component: database
• Component: test

Let me know if more details are needed!

[wakeful]

hey, @ErezWeiss

Just to clarify your request: should that exclusion be a global filter (applied across all resources), or are you looking for the possibility to set this per resource, e.g.?

s3:
  exclude:
    ifTagExist: Component