Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom connected_endpoints_keys #4929

Open
1 task done
PieterL75 opened this issue Jan 24, 2025 · 0 comments
Open
1 task done

custom connected_endpoints_keys #4929

PieterL75 opened this issue Jan 24, 2025 · 0 comments
Labels
type: enhancement New feature or request

Comments

@PieterL75
Copy link

PieterL75 commented Jan 24, 2025

Enhancement summary

When defining a new set of custom connected_endpoints_keys, we have to copy over the defaults
as per https://avd.arista.com/5.1/roles/eos_designs/docs/input-variables.html?h=connected_endpoints_keys#connected-endpoints-keys-settings

can we have a custom_connected_endpoints_keys, similar like the custom_node_type_keys that simply merges ?

Which component of AVD is impacted

eos_designs

Use case example

Define an extra connected_endpoints_keys for specific devices

Describe the solution you would like

Create a new groupvar custom_connected_endpoints_keys
# These values will be combined with the defaults; custom connected endpoints keys named the same as a default connected endpoints_keys will replace the default

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
@PieterL75 PieterL75 added the type: enhancement New feature or request label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant