We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
adding a include or exclude filter via resource-types in the config file seems to have no effect.
include
exclude
resource-types
resources are checked and removed anyway.
example config:
resource-types: include: - foo exclude: - S3Bucket
i've added a printf after the yaml.Unmarshal in config.go and the returned values are empty:
yaml.Unmarshal
config.go
ResourceTypes:{Targets:[] Excludes:[]}}] ResourceTypes:{Targets:[] Excludes:[]}
I guess this is caused because types.Collection is used for these values and there seems to be no custom unmarshaler for this type.
types.Collection
The text was updated successfully, but these errors were encountered:
It actually is excludes and targets. Where did you get the names from? I found one occurrence of exclude and fix it in #171.
excludes
targets
Another issue is that aws-nuke should print an error when there is an unknown config field.
Sorry, something went wrong.
Afaik Unmarshal will just ignore them, but UnmarshalStrict should bring the desired behaviour.
b57eb5e
Merge pull request #172 from Sixt/master
2432890
fix more typos - fixes #170
No branches or pull requests
adding a
include
orexclude
filter viaresource-types
in the config file seems to have no effect.resources are checked and removed anyway.
example config:
i've added a printf after the
yaml.Unmarshal
inconfig.go
and the returned values are empty:ResourceTypes:{Targets:[] Excludes:[]}}] ResourceTypes:{Targets:[] Excludes:[]}
I guess this is caused because
types.Collection
is used for these values and there seems to be no custom unmarshaler for this type.The text was updated successfully, but these errors were encountered: