feat: Add placeholders for NAP 5.6 / 4.14 release notes #284
Conversation
This file contains 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
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
mjang
added a commit
that referenced
this pull request
Apr 1, 2025
* Nap helm chart (#267) * feat: install nap 5 with helm chart * Update content/nap-waf/v5/admin-guide/deploy-on-kubernetes/deploy-with-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> * feat: Add placeholders for NAP 5.6 / 4.14 release notes (#284) * feat: Restructure Kubernetes documentation IA, update references * feat: Re-order admin-guide pages * Update content/nap-waf/v4/releases/about-4.14.md * feat: Remove unnecessary item, move issues from known to resolved * feat: Update Generated Documentation (#301) Compiler 11.322.0-nap-release-4-14-0-13891737 (6d34e452) * Apply suggestions from code review Co-authored-by: ohad-perets <126083286+ohad-perets@users.noreply.github.com> * feat: Update package names, move Go version bump to resolved issues * feat: Convert K8s configuration to includes for both cases * feat: Remove mention of Alpine 3.17 * feat: OS version consolidation, remove redundancy * feat: Add JWT step using includes * feat: Update text to be imperative * feat: Additional tab work for NAP5 installation * feat: Fix formatting of common steps * feat: Update release dates * Update deploy-on-docker.md removing && from DanielK's comments * Update deploy-on-docker.md remove also for plus * feat: Update package file versions * feat: Push additional documentation improvements * feat: Fix links * Update content/nap-waf/v5/releases/about-5.4.md * Update deploy-with-helm.md remove mtls & read-only references due to a bug, need to fix that after release * Update deploy-with-helm.md update login with jwt --------- Co-authored-by: liadlevif5 <118743780+liadlevif5@users.noreply.github.com> Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> Co-authored-by: ohad-perets <126083286+ohad-perets@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
Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:
Problem: Give a brief overview of the problem or feature being addressed.
Solution: Explain the approach you took to implement the solution, highlighting any significant design decisions or
considerations.
Testing: Describe any testing that you did.
Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.
If this PR addresses an issue on GitHub, ensure that you link to it here:
Closes #ISSUE
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdandCHANGELOG.mdFootnotes
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. ↩