Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config file with only exclude rules do not work as expected #198

Closed
yorinasub17 opened this issue Jun 25, 2021 · 0 comments · Fixed by #209
Closed

Config file with only exclude rules do not work as expected #198

yorinasub17 opened this issue Jun 25, 2021 · 0 comments · Fixed by #209
Assignees
Labels
bug Something isn't working

Comments

@yorinasub17
Copy link
Contributor

I don't remember if this was intentional or not.

If you create a config file where there is only an exclude rule, intuitively this should mean "include everything but what is requested to be excluded," but in practice this becomes "exclude everything" because cloud-nuke treats empty include rules as "include nothing."

You can work around this by adding an explicit include rule to include everything:

s3:
  include:
    names_regex:
      - ".*"
  exclude:
    names_regex:
      - "^my-real-s3-bucket$"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants