How to format cloud-nuke --config file to blanket-exclude resource types #867
Unanswered
paperpiedpiper
asked this question in
How do I
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm trying to use Cloud Nuke in a GitHub Actions workflow to regularly clean up AWS resources, but I keep running into issues with the command length and resource type exclusions.
I want to exclude a large set of resource types (IAM, VPC, S3, etc.) and have been passing them as --exclude-resource-type flags, but the command has gotten too big and gets truncated. I understand from your documentation and the example config file that exclusions can be managed via a YAML config, but I'm not sure how to translate my current list of exclusions into the correct config file format. To be honest, I'm having trouble following the examples over at: https://github.com/gruntwork-io/cloud-nuke/tree/master/config/examples
Could you please advise:
What is the recommended way to exclude a long list of resource types in a config file?
Is there a minimal example config for just excluding specific resource types (no regex, no tags, just blanket exclusion)?
Here’s a snippet of my workflow and the resource types I want to exclude (see below):
Is it going to be something like this?:
Any help or example config would be greatly appreciated!
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions