-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zebra rework factor #15473
Closed
+603
−547
Closed
Zebra rework factor #15473
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
9ba9ece
zebra: factorise 'show nexthop-group rib' nexthops
pguibert6WIND 2cdabcd
zebra: move early rib_evpn_route_[add/delete]() function in early_ fu…
pguibert6WIND 0d41b06
zebra: move route_entry_dump_nh() into route_entry_dump_nhg()
pguibert6WIND 961e57c
zebra: rework show_nexthop_group_out_nexthop() separate function
pguibert6WIND 99cbc1a
zebra: rework 'vty_show_ip_route()' function
pguibert6WIND 11ed7c1
zebra: rework zsend_redistribute_route() function with nhg
pguibert6WIND 127255a
zebra: rework mpls uninstall based on nexthop group
pguibert6WIND 5f6520d
zebra, lib: move nexthop display helper to lib folder
pguibert6WIND File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Part of the reason I've never moved to having a vty function and a json function is that you end up with code that is in two functions and an addition to the data structure being dumped is easy to forget the json aspect of it ( or vice versa ). It always sucked but I felt the in your face aspect was warranted. What advantage are you looking for with this change? How do we ensure that a new developer is going to remember to hit both sides of the equation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to factor some changes for the BGP NHG changes. but it seems I no longer need to support it.
So I try to upstream it.
I admit most of the code change is not justified, today.
A little more work could help in having a single function.
A single function could help, to handle both json and vty.