NGF Add docs for WAF PLM#2112
Draft
bjee19 wants to merge 4 commits into
Draft
Conversation
Contributor
Author
|
@travisamartin, these are the docs for NGF WAF PLM, the todo link for plm setup and AP resources configuration is still there. However, the other portions for NGF related setup should be completed and ready for review. Just wanted to give you a heads up, once the PLM docs are completed, we'll fill in those empty links. |
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
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
WAF using PLM requires documentation. Basic knowledge on AP resources should be present in the NGF docs, however the F5 WAF PLM docs should be referenced for all other details.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩