Skip to content
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

App Protect WAFv5 compatibility matrix #6178

Conversation

nginx-bot
Copy link
Contributor

Proposed changes

Screenshot 2024-08-12 at 15 34 14

  • Add NIC WAF v5 matrix

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto main
  • I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

@nginx-bot nginx-bot requested review from a team as code owners August 13, 2024 08:54
@nginx-bot nginx-bot added dependencies Pull requests that update a dependency file documentation Pull requests/issues for documentation needs cherry pick Cherry pick this PR into a release branch labels Aug 13, 2024
@github-actions github-actions bot removed the dependencies Pull requests that update a dependency file label Aug 13, 2024
@vepatel vepatel merged commit d5b9970 into release-3.6 Aug 13, 2024
41 checks passed
@vepatel vepatel deleted the cherry-pick-release-3.6-ecb5b9b2de28b1e8452825fdc189454bd215d27b branch August 13, 2024 09:01
@pdabelf5 pdabelf5 changed the title [cherry-pick] Docs/wafv5 cfgmgr enfrcr App Protect WAFv5 compatibility matrix Aug 16, 2024
@pdabelf5 pdabelf5 removed the needs cherry pick Cherry pick this PR into a release branch label Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Pull requests/issues for documentation
Projects
Status: Done 🚀
Development

Successfully merging this pull request may close these issues.

3 participants