feat: Add Alpine 1.19 support to NGINX App Protect WAF documentation #109
Conversation
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
As part of the NGINX App Protect WAF 5.5 release, Alpine 1.19 support has been added. This commit updates the relevant sections of documentation that mention Alpine support, while also fixing up the metadata for some related pages.
✅ Deploy Preview will be available once build job completes!
|
mjang
added a commit
that referenced
this pull request
Jan 30, 2025
* Add documentation for UDS converter in NAP5 (#110) * feat: Add Alpine 1.19 support to NGINX App Protect WAF documentation (#109) As part of the NGINX App Protect WAF 5.5 release, Alpine 1.19 support has been added. This commit updates the relevant sections of documentation that mention Alpine support, while also fixing up the metadata for some related pages. * Update configuration.md with bf section (#115) add brute force configuration * WAF enforcer-only upgrade comment (#116) * Update Generated Documentation (#118) doc: Update policy schema Compiler 11.246.0-nap-release-4-13-0-13336475 (7fab3dc1) * feat: Additional updates/fixes for NAP 5.5 release (#121) * Update install.md (#122) fix some alpine v4 misses * Add directory warning, fix UDS issue (#124) * feat: Add Update App Protect Signatures placeholder section (#125) * feat: Add 5.5/4.13 release note placeholders, update frontmatter (#126) * Update policy.html (#127) * Update policy.html * Update policy.html fix some lines and remove more tables * Update policy.html clean the code * feat: Remove deprecated NAP EA theme files, update release notes (#133) * Update install.md (#134) resharp the comment for an upgrade to a specific version of AS/BS/TC * Update compiler.md (#137) adding a note to upgrade to a specific version * Update configuration.md (#144) * Ohad perets patch 3 (fixing some PM comments) (#149) * Update about-4.13.md * Update about-5.5.md * Update compiler.md * feat: Update versioning based on feedback * Update about-5.5.md (#150) * feat: Update 5.5 release note link for user-defined signatures * Update about-4.13.md (#151) * Update configuration.md (#152) * Update configuration.md (#153) --------- Co-authored-by: mouraddmeiri <67323028+mouraddmeiri@users.noreply.github.com> Co-authored-by: ohad-perets <126083286+ohad-perets@users.noreply.github.com> Co-authored-by: mikegoltsman <157731722+mikegoltsman@users.noreply.github.com> Co-authored-by: Mike Jang <3287976+mjang@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
As part of the NGINX App Protect WAF 5.5 release, Alpine 1.19 support has been added. This commit updates the relevant sections of documentation that mention Alpine support, while also fixing up the metadata for some related pages.
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdandCHANGELOG.md)Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation.
Please refer to our style guide for guidance about placeholder content.