Repository navigation
enhanced PushConfig function to make otg ports up during push config.… - #157
Open
abhijit-dhar wants to merge 3 commits into
Open
abhijit-dhar wants to merge 3 commits into
abhijit-dhar wants to merge 3 commits into
Conversation
… Also provided alternative function to skip it if required PushConfigOpts()
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.
PushConfig now brings up port links automatically after applying the configuration. Previously, it preserved the existing port link state and did not alter port status.
To restore the earlier behavior when required, support has been added for PushConfigOptions{LinkUp bool} along with the new PushConfigOpts(t, cfg, opts) API. When opts is nil or LinkUp is set to false, the link-up step is skipped, preserving the current port state. When LinkUp is true, port links are explicitly brought up after the configuration is pushed.
This provides backward-compatible flexibility, allowing users to maintain the previous status-quo behavior while enabling explicit port link activation when desired.