[IOS-XR] Fix show l2vpn bridge-domain detail
: Parses variations in the EVI field format correctly
#907
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.
p63
regex inshow_l2vpn.py
to support optional suffix (e.g., "(SRv6)") for EVI valuesgolden9_expected.py
to reflect new test output for EVI fieldgithub_parser.json
for the updated line referenceThese changes enhance the parser's compatibility with new formats in
ShowL2vpnBridgeDomainDetail
.Description
The
ShowL2vpnBridgeDomainDetail
parser for IOS-XR devices was not handling some variations in the EVI field format correctly, resulting in parsing errors or missed data. Specifically, when the evi field includes additional suffix information (e.g., (SRv6)), the parser could not match this pattern and failed to extract the EVI value.Motivation and Context
Closes #906
Checklist: