-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
WAFv2: Added support for custom response bodies #19764
WAFv2: Added support for custom response bodies #19764
Conversation
30 days open on this pr, a missing feature set for sure. thanks @andyalm for doing this work. |
this is exactly what I am looking for, any update on when this will be released? |
Good enhanced by @andyalm and very useful, but lost because nobody review it. |
@andyalm thanks for doing this... would love to use this. Not sure how we can help prioritize it. Let me now if there is anything we can do to help move this along. |
We need this feature! |
@KFoxder @jonnyshaw89 thanks for chiming in. I wish I knew how to get a review on this change. I've got two PR's that have been open for more than a month. As far as I know, I have done all of the steps on the checklist to get a review. From time to time, I have to resolve conflicts that appear in |
@bflad @breathingdust @YakDriver Is there any way we can help prioritize a review on this? |
We need this feature too! Maybe the problem is that there is no open issue for this? The original issue #18754 is closed although this PR is not merged yet. Can anybody reopen this issue please? |
This is exactly what I need! Thanks for your great work @andyalm |
@hc-github-team-terraform-aws Please could we get a review on this? |
Please review, in much need of this also. Thanks. |
is this available in the current release ? |
Also here because I need this missing feature. @hc-github-team-terraform-aws could you please review? Would it be possible to delegate some maintainer rights to active external contributors? |
Folks, how is that possible to expedite this? We need the feature very much!!! |
Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding. Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author. For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000. For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide. |
…-custom-response-body
0313665
to
8c0d773
Compare
Thanks for the heads up @zhelding. I've updated my changes to work with the new file structure and its passing all checks again. Is there anything else I need to do to get a review? |
Hi @andyalm. No further action is required on your end for merging this pull request. This pull request will now be addressed via our standard prioritization process. Unfortunately, given the large quantity of issues and pull requests we receive, we are not always able to review every pull request in a timely manner. We prioritize contributions that provide the greatest value to the largest number of users -- which we primarily infer based on the number of 👍 reactions. Additionally, an explanation of the particular use case for a contribution can provide information on how the changes might be useful in a broader context. You can get a view of the wider development plans for the provider via our road map, published quarterly. Thank you again for your contribution and your patience. |
Hi all 👋 Just letting you know that this is issue is featured on this quarters roadmap. If a PR exists to close the issue a maintainer will review and either make changes directly, or work with the original author to get the contribution merged. If you have written a PR to resolve the issue please ensure the "Allow edits from maintainers" box is checked. Thanks for your patience and we are looking forward to getting this merged soon! |
e243785
to
eae0375
Compare
Thanks again @andyalm for contributing to this feature! 🚀 Output of acceptance tests:
|
This functionality has been released in v3.67.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
This adds support for adding custom response bodies to both the
aws_wafv2_web_acl
andaws_wafv2_rule_group
resources. Here is an example:This is marked as a draft as I still need to update the documentation and release notes.
Community Note
Relates OR Closes #18754
Output from acceptance testing: