Initial WAF support for NGINXaaS for Google#1939
Open
edarzins wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
syousF5
approved these changes
May 7, 2026
JTorreG
reviewed
May 12, 2026
Contributor
JTorreG
left a comment
JTorreG
left a comment
There was a problem hiding this comment.
use the ref shortcode for links to docs.nginx.com
amudukutore
reviewed
May 12, 2026
Support for enabling WAF per deployment, NGINX configurations with WAF, and WAF logging.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support for enabling WAF per deployment, NGINX configurations with WAF, and WAF logging.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
@richbrowne @JTorreG
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩