Refactor(eos_designs): Make Flow tracking enabled on Dps1 interface only #3767
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
state: CI Updated
ClausHolbechArista
approved these changes
Mar 25, 2024
ClausHolbechArista
added
the
one approval
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
After discussion with engineering, enabling by default Flow tracking for WAN design scenario only on Dps1 interface to keep sane default.
It can be enabled on WAN and LAN interfaces depending on the design and scale using custom_structured_configuration.
Component(s) name
arista.avd.eos_designsProposed changes
Cf summary
How to test
molcule
Checklist
Repository Checklist