-
Notifications
You must be signed in to change notification settings - Fork 50
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
add wafv2 permissions #136
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need a terminator class for every module but we do need one for every resource that isn't already covered. I only took a quick look at your PRs, looks like you have webacl and ipset resources which would need classes, did I miss any?
@jillr yes :)
I've added a draft for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re created:
list_ip_sets doesn't return any information about creation time. The DbTerminator class records the first time it sees an object and automatically approximates the age based off of this first encounter.
Re regional vs cloudfront:
_create generates a list of objects, each class can simply run both the boto3 list actions and combine the two lists.
Co-authored-by: Mark Chappell <mchappel@redhat.com>
Co-authored-by: Mark Chappell <mchappel@redhat.com>
450 passes with the policies in this latest revision but the terminator classes still fail when a resource exists.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally, including a termination (I added a 2 minute age limit and used the tests in 450). Everything looks good to me now, thanks very much for this one @markuman!
Will deploy after merge.
Required for