[Nexthop][fboss2-dev] Document the difference between set and config operations - #1621
Open
benoit-nexthop wants to merge 1 commit into
Open
benoit-nexthop wants to merge 1 commit into
benoit-nexthop wants to merge 1 commit into
Conversation
Update fboss_cli.md with an explanation of the differences between `set` and `config` and what one should expect from each command. # Summary This adds some additional text to `fboss_cli.md` detailing the differences between the fboss2(-dev) `set` and `config` commands. # Test Plan No test additions / changes. Confirmed with visual inspection of the generated output using docusaurus. Co-Authored-By: steve ulrich <sulrich@nexthop.ai>
Contributor
Author
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
1 participant
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.
Summary
This adds some additional text to
fboss_cli.mddetailing the differences between thefboss2/fboss2-devsetandconfigcommands, and what one should expect from each:setis a runtime-only write via a thrift client to the running agent; nothing is persisted.configedits the configuration file through a staged session and is persisted on commit.configcommit or reload (or a warm/cold boot) re-applies config and reverts anyset.setchanges are invisible toconfig session diff/config history.Test Plan
Docs-only change; no test additions or changes. Confirmed with visual inspection of the generated output using docusaurus.
Co-Authored-By: Steve Ulrich sulrich@nexthop.ai