Fix: allow integer values in ext_community_list_raw field for Arista BGP… #306
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
cooperwinser
changed the title
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.
Description
Fix: allow integer values in ext_community_list_raw field for Arista BGP parsing
This fix resolves validation errors by modifying the parsing logic to accept both integer and string types for the 'ext_community_list_raw' field in Arista device BGP route data.
Related Issues
Fixes #305
Motivation and Context
The current implementation strictly requires string inputs for ext_community_list_raw, causing validation errors when integer values are received from Arista devices. We were experiencing this issue ourselves and these changes appear to have resolved the issue.
Tests