Feat(eos_designs): Exclude l3_edge neighbors from peer_group #4491
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
When
routing_protocol
is set toebgp
andinclude_in_underlay_protocol
is set tofalse
for anl3_edge
link, previously it was not rendered in BGP. It is now rendered into BGP without using the default underlay peer group.Related Issue(s)
Partially fixes #4379
Component(s) name
arista.avd.eos_designs
Proposed changes
Only render the peer group if
include_in_underlay_protocol
is set totrue
.How to test
Using the dual-dc-l3ls example topology you can modify the
l3_edge
include_in_underlay_protocol
androuting_protocol
values in theFABRIC.yml
group_var.Checklist
User Checklist
Repository Checklist
Additional
I can add tests for this to molecule. I'm not sure if what the scope of the molecule tests are for the AVD project, and if we want every edge case covered or not. Additionally, while this behavior feels intuitive to me, I can explicitly add an example to the documentation, but documenting an edge case like this could be considered clutter so I didn't add anything yet.