Update N1 API docs: add staged config one.json changes #85
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
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
vivki
changed the title
vivki
changed the title
ADubhlaoich
approved these changes
Jan 22, 2025
|
@vivki You need to accept the F5 CLA: there's also a merge conflict to resolve! |
FYI, I've been following the sequence of MRs from the source repo, and have resolved the conflict. @vivki , you do need to follow the instructions in #85 (comment) |
|
recheck |
|
I have hereby read the F5 CLA and agree to its terms. |
|
recheck |
|
I have hereby read the F5 CLA and agree to its terms |
|
recheck |
mjang
approved these changes
Jan 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Proposed changes
This PR updates the API docs for the Staged Configs epic. Also wraps some incremental changes made recently.
Checklist
Before creating a PR, run through this checklist and mark each as complete.
I have read the contributing guidelines
I have signed the F5 Contributor License Agreement (CLA)
If applicable, I have added tests that prove my fix is effective or that my feature works
If applicable, I have checked that any relevant tests pass after adding my changes
I have updated any relevant documentation (
README.mdandCHANGELOG.md)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
If the change involves:
<username>in place of PIIIn these cases, the change will require at least two (2) approvals before merging