feat(huawei): structured BGP route output (4/10) - #367
Open
WilhelmZA wants to merge 1 commit into
Open
Conversation
WilhelmZA
force-pushed
the
pr/huawei-structured-bgp
branch
from
June 14, 2026 11:11
d1104f8 to
8648bad
Compare
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.
Summary
Adds structured BGP route output for Huawei VRP, parsing
display bgp routing-tabledetail (routes, AS-path, communities, RPKI/origin) into the standard structured table, and registershuaweias a structured-capable platform.models/parsing/huawei.py+bgp_routestr_huaweioutput plugin; hardens the existingbgp_route_huaweiinput transform against non-list/invalid targets.Stacked series (4/10). Builds on
pr/bgp-community-names.Addresses
Adds structured Huawei BGP-route parsing and hardens the input transform (accepts a string or list target and tolerates non-prefix input). Intended to resolve the following upstream issues — confirmation on the affected hardware would be appreciated: