updated template to catch NSR N/A state #381
Merged
Conversation
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
|
Thanks @Warsenius |
jvanderaa
pushed a commit
that referenced
this pull request
Nov 10, 2021
The template does not account for an NSR state of "N/A". This updates the template to support more than one character for NSR value. TEMPLATE UPDATE: - Update ``NSR`` capture group from "(\w)" to "(\S+)" - Update Record line to include EoL marker ``\s*$$`` TEST FILES: - Update raw and parsed files to include an NSR value if "N/A"
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.
ISSUE TYPE
COMPONENT
cisco_xr_show_mpls_ldp_neighbor_brief.template
SUMMARY
i had a mpls neighbor with a NSR field as "N/A".
Updated template to catch this.