When adding a vrf into the management_ssh, the "use_mgmt_interface_vrf" is not translated to the name of the vrf used in the management interface.
This is the case for SNMP, NTP and other base settings.
As a user, I would like to be able to use "use_mgmt_interface_vrf" in any 'vrf' definition where possible
Which component of AVD is impacted
eos_designs, eos_cli_config_gen
Use case example
Have a generic reference to the name defined for the management vrf is easy and straightforward.
Otherwise we'll have to use the "use_mgmt_interface_vrf" in one case, and the real vrf name in another case.
This can be easily overlooked
Describe the solution you would like
Provide one way to reference the management interface vrf name.
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide
[X] I agree to follow this project's Code of Conduct
Enhancement summary
When adding a vrf into the management_ssh, the "use_mgmt_interface_vrf" is not translated to the name of the vrf used in the management interface. This is the case for SNMP, NTP and other base settings.
As a user, I would like to be able to use "use_mgmt_interface_vrf" in any 'vrf' definition where possible
Which component of AVD is impacted
eos_designs, eos_cli_config_gen
Use case example
Have a generic reference to the name defined for the management vrf is easy and straightforward. Otherwise we'll have to use the "use_mgmt_interface_vrf" in one case, and the real vrf name in another case. This can be easily overlooked
Describe the solution you would like
Provide one way to reference the management interface vrf name.
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide