-
Notifications
You must be signed in to change notification settings - Fork 398
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
Extended the wafv2_web_acl module with custom_response_bodies argument #721
Extended the wafv2_web_acl module with custom_response_bodies argument #721
Conversation
I believe I addressed all issues now. Let's see if build goes through now. Once green this should be ready to be merged. |
Sanity is failing
|
Fixed RETURN docs now. However I also noticed other CI errors in integration tests:
This probably happens because of old boto or s.th. But what is weird that it also fails on params that were already there before my changes, such as VisibilityConfig. |
When newer botocore/boto3 versions are necessary, we can install them like https://github.com/mediafellows/community.aws/blob/wafv2_web_acl_improvements/tests/integration/targets/aws_msk_config/tasks/main.yml#L20
Indeed, I have no idea atm. |
@stefanhorning That may be a result of #644 landing and forcing the tests to run against the oldest version of botocore that we support, to highlight issues like this. Unfortunately if the code wasn't exercised before the tests wouldn't highlight the issue... We actually have an even easier way to setup the boto3 pip installation (I still need to refactor community.aws) https://github.com/ansible-collections/amazon.aws/blob/main/tests/integration/targets/ec2_vol/meta/main.yml |
I will try to use the pip role then. I am unfortunately not yet sure which botocore version introduced this, just for the boto3 lib I know which version, it seems to be the 1.18.0. See https://boto3.amazonaws.com/v1/documentation/api/1.18.0/reference/services/wafv2.html#WAFV2.Client.create_web_acl Should I also add a note to the module docs and/or a check for correct boto version in the code? |
try botocore 1.20.40 That seems to be to 'blame' for the CustomResponseBodies definition:
|
Ok, found out through github project that boto3 1.18.0 depends on botocore 1.21.0, see https://github.com/boto/boto3/blob/1.18.0/setup.cfg So I will try with that |
Once you determine the minimum requirements, please do update the docs and code to cleanly fail: See for example:
|
Addressed all comments now I hope. Let's see what CI thinks. |
Sorry, completely forgot about this PR. Have applied @tremble s suggestion now to check botocore version directly in main. Hope we are good to merge then (might still need a rebase though). |
2b7b13a
to
4b20420
Compare
…estsuite. Bumped version_added for new feature.
…h newever botocore)
…as its only depedency setup in the wafv2 target Syntax fixing in create_webacl.yml test play
a804714
to
a113218
Compare
Got the extra test working now (for custom_response_bodies deletion). Also rebased on latest main to squash all irrelevant commits and get rid of merge commits. So in my opinion this can finally get merged. |
Build succeeded.
|
Ah one last change request. You created an addition webacl. And you can verfiy the removal when you read-out the web acl again with its '_info` module
|
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.
@stefanhorning Thank you for taking time to work on this. I agree with @markuman suggested. Other than that, LGTM!
Build succeeded.
|
@markuman @alinabuzachis added the extra test and cleanup task now without breking the build again. 🎉 |
111 conversations, that's a number :) |
Yeah, it's probably the longest PR of all Ansible PRs that only add one param to a module. :) |
Build succeeded (gate pipeline).
|
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #934 🤖 @patchback |
#721) Extended the wafv2_web_acl module with custom_response_bodies argument SUMMARY Extended the wafv2_web_acl module to also take the custom_response_bodies argument, improved docs and extended tests ISSUE TYPE Feature Pull Request COMPONENT NAME wafv2_web_acl ADDITIONAL INFORMATION Also touched docs of aws_waf_web_acl to make it easier to find the WAF v2 modules as I had trouble finding that at first. Reviewed-by: Markus Bergholz <git@osuv.de> Reviewed-by: Stefan Horning <None> Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> (cherry picked from commit c91acf6)
#721) (#934) [PR #721/c91acf6a backport][stable-3] Extended the wafv2_web_acl module with custom_response_bodies argument This is a backport of PR #721 as merged into main (c91acf6). SUMMARY Extended the wafv2_web_acl module to also take the custom_response_bodies argument, improved docs and extended tests ISSUE TYPE Feature Pull Request COMPONENT NAME wafv2_web_acl ADDITIONAL INFORMATION Also touched docs of aws_waf_web_acl to make it easier to find the WAF v2 modules as I had trouble finding that at first.
ec2_instance incr version added to 3.3.0 for added parameters SUMMARY CI problems in backport-3 ansible-collections#721 And we don't won't to stop 3.2.0 release. Let's try to put/backport it for the next release. ISSUE TYPE Docs Pull Request COMPONENT NAME ec2_instance Reviewed-by: Gonéri Le Bouder <goneri@lebouder.net> Reviewed-by: Mark Chappell <None>
…ctions#852) ec2_instance: metadata_options version_added increased SUMMARY After CI troubles in the past, we've forget to backport this feature. incr from 3.2.0 to 3.3.0 ansible-collections#763 failed backport 3 PR for 3.2.0 release ansible-collections#721 initial implementation for 3.2.0 ansible-collections#715 therefore no changelog fragment is necessary. ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_instance ADDITIONAL INFORMATION Reviewed-by: Jill R <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: Mark Chappell <None>
SUMMARY
Extended the
wafv2_web_acl
module to also take thecustom_response_bodies
argument, improved docs and extended testsISSUE TYPE
COMPONENT NAME
wafv2_web_acl
ADDITIONAL INFORMATION
Also touched docs of
aws_waf_web_acl
to make it easier to find the WAF v2 modules as I had trouble finding that at first.