-
Notifications
You must be signed in to change notification settings - Fork 3
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
aws-nuke-exporter doesn't report lines lacking ID or complete Details #3
Comments
Thank you for reaching out with your concerns and observations regarding the
Regarding the resource type Your feedback is invaluable in helping us enhance the tool's functionality and reliability. Please feel free to provide any additional information or examples regarding the second point, and I'll do my best to address it promptly. Thank you for your contribution to making |
Thanks for your very prompt response and the 1.0.3 release, which resolved the problems in two of the cases. However, it didn't correctly handle the missing ID or truncated Detail cases correctly, placing those into RemovalStatus:
Also, the sample TXT output for the missing ID case had an ID with Anyhow, I came up with PR #6, which handles all the sample cases pretty reasonably (there's no perfect solution for truncated output). Unfortunately you can't use the same name for multiple match groups, which complicates the code a bit, but it's not too painful. |
A quick google search turned up the reason for the typo |
The
sample_output
folder demonstrates this for two of the three cases:-
is omitted:aws-nuke only prints details when it is possible to filter based on properties. Not all resource types support this.
]
is omitted (scroll right to see<<OutputTruncated>>
):Apparently, sometimes the Details data gets too long and is truncated? I haven't seen this, but it is in your samples.
Some resource types don't have an ID that can be used for filtering, and aws-nuke can only filter with properties. For these, aws-nuke doesn't print an ID, but just skips ahead to Details.
The above cases should be sufficient for test purposes, but I can provide some more (obfuscated) examples.
An entry of particular interest is the one for the resource type
NetpuneSnapshot
(sic). I don't know if this is an aws-nuke error or a bug in the boto code, or in the AWS API itself, nor whether you can use that type for filters (and if you can, whether the filter works correctly). This would bear further investigation, but I dont have time right now.Here is a more extensive list
The text was updated successfully, but these errors were encountered: