Add support for the configuration of Connectivity Fault Management data model and associated config generation.
Which component of AVD is impacted
eos_cli_config_gen
Use case example
We would like to be able to define CFM profiles in the vars to be able to generate the config & documentation for said profiles through AVD.
Reference to the TOI documentation :
New templates to generate the associated configuration & documentation
Describe alternatives you have considered
At the moment the only solution is to add all the configuration in eos_cli as raw eos commands. The downside is that the config appears at the bottom, instead of at the right place. It also does not get validated, risking typos/issues making it through to the switch.
Additional context
No response
Contributing Guide
[X] I agree to follow this project's Code of Conduct
Enhancement summary
Add support for the configuration of Connectivity Fault Management data model and associated config generation.
Which component of AVD is impacted
eos_cli_config_gen
Use case example
We would like to be able to define CFM profiles in the vars to be able to generate the config & documentation for said profiles through AVD. Reference to the TOI documentation :
Describe the solution you would like
Describe alternatives you have considered
At the moment the only solution is to add all the configuration in
eos_cli
as raw eos commands. The downside is that the config appears at the bottom, instead of at the right place. It also does not get validated, risking typos/issues making it through to the switch.Additional context
No response
Contributing Guide