Fix(eos_cli_config_gen): Ensure unique VRF names in schemas #2878
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
github-actions
bot
added
role: eos_cli_config_gen
ClausHolbechArista
added
the
cherry-pick-for-3.8.x
carlbuchmann
removed
the
cherry-pick-for-3.8.x
carlbuchmann
pushed a commit
to carlbuchmann/avd
that referenced
this pull request
Jul 13, 2023
gmuloc
pushed a commit
that referenced
this pull request
Jul 20, 2023
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.
Change Summary
Ensure unique VRF names in schemas
Component(s) name
arista.avd.eos_cli_config_genProposed changes
A few schemas did not enforce unique VRF names by leveraging
primary_keyin the schema.This affects the ability to properly merge
custom_structured_configurationfromeos_designs.How to test
No changes to anything, since we should already be configuring this correctly.
Checklist
User Checklist
Repository Checklist