Fix handling of optional fields in get_bgp_peer function #3565
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.
What I did
This commit fixes an issue in get_bgp_peer function where
local_addr
andname
were treated as mandatory. However,local_addr
andname
fields are not required in BGP neighbor configuration.How I did it
The local_addr and name fields are no longer mandatory in the get_bgp_peer function.
How to verify it
Apply BGP neighbor configuration like below (utilizing BGP_PEER_GROUP), where fields such as local_addr or name are omitted:
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)
Fixes #19930