-
Notifications
You must be signed in to change notification settings - Fork 403
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_ip_set module #449
Conversation
aws terminator needs rw access to wafv2
|
There are failures that are not related with my PR
|
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.
This PR will need a changelog.
meta/runtime.yml is causing ci_complete to be run, if you have issues with the tests timing out or exceeding request limits give me a ping on irc and I can rerun them (a few are still failing now, but they're nothing to do with this change)
recheck |
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.
lgtm when tests are passing
recheck |
there are still so many failures which are not related to this PR. How can we made them pass? |
Required: ansible/ansible#73975 for pass 2.9 integration tests |
Thanks for putting so much work into these new modules, they look great 😃 I just wanted to mention that once 2.9 becomes security-only, new modules shouldn't be too much of a hassle to test in CI with YAML anchors + module_defaults actions. It should just be an additional two lines for a new module, like
(But don't worry; #73975 will be included in the upcoming final non-only-security 2.9 cycle, it just hasn't been added yet because those get merged in batches by the release engineer) |
@s-hertel what worries me about using the YAML Anchors is that this will mean that when someone forgets to update the group in runtime.yml the integration tests won't catch it. This is a really poor experience for collection maintainers. |
Test failures are due to known flakes. WAF tests are running cleanly and taking around 10-20 seconds. |
Thanks for your work on this @markuman sorry it's taken a while to get everything merged. |
* add wafv2 ip set module * expand meta/runtime with wafv2_ip_set modules
* add wafv2 ip set module * expand meta/runtime with wafv2_ip_set modules
* add wafv2 ip set module * expand meta/runtime with wafv2_ip_set modules
…nsible-collections#450) Add botocore requirements to s3_bucket ownership control management SUMMARY (get|set|delete)_bucket_ownership_controls requires botocore >= 1.18.11 Because we state our minimum supported version of botocore is 1.16.0 we need to explicitly call this requirement for management of bucket ownership controls. ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_bucket ADDITIONAL INFORMATION fixes: ansible-collections#449 Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
SUMMARY
Add new module to handle wafv2 ip sets.
ISSUE TYPE
COMPONENT NAME
wafv2_ip_set
wafv2_ip_set_info