We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I want to use the endpoint_port_channel variable from the adapters / endpoint_ports / port-channels in my interface J2 templates. https://avd.arista.com/5.2/ansible_collections/arista/avd/roles/eos_designs/docs/input-variables.html#context-for-interface_descriptions-templates shows that this variable is not there.
connected_endpoints_port_channel_interfaces: {{ peer }} {{ adapter_port_channel_id }} {{ adapter_port_channel_description }} {{ adapter_description }} All group/hostvars
It should be in the AVD string formatter, but that is not something I can use for this.
eos_designs
Use the endpoints/adapters/endpoint_ports/port-channels/endpoint_port_channel variable in the type/interface_descriptions/jinja2 templates
Expose that varialbe in the jinja2 engine
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Enhancement summary
I want to use the endpoint_port_channel variable from the adapters / endpoint_ports / port-channels in my interface J2 templates.
https://avd.arista.com/5.2/ansible_collections/arista/avd/roles/eos_designs/docs/input-variables.html#context-for-interface_descriptions-templates
shows that this variable is not there.
It should be in the AVD string formatter, but that is not something I can use for this.
Which component of AVD is impacted
eos_designs
Use case example
Use the endpoints/adapters/endpoint_ports/port-channels/endpoint_port_channel variable in the type/interface_descriptions/jinja2 templates
Describe the solution you would like
Expose that varialbe in the jinja2 engine
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide
The text was updated successfully, but these errors were encountered: