eos_cli_config_gen/pyavd: generate configlets instead of monolithic configs #5339
|
Hi, for customers requesting separate configlets (aaa, routing, management ...) instead of one monolithic device configuration i am currently using my own jinja templates and python scripts to generate those configlets from the avd generated structured configuration. |
Replies: 3 comments 3 replies
|
We do not have any builtin way of splitting the configuration into separate configlets, but if you break up the structured config in smaller parts (in a new task between eos_designs and eos_cli_config_gen), you can run |
|
I solved this issue in AVD version 5.0 using 'structured_config_filename' and 'read_structured_config_from_file' as input to eos_cli_config_gen. In AVD v6.x these input variables are gone and hence no chance to get this solution working that way. Is there any workaroud available ? |
|
I solved this with a playbook containing 2 plays. |
Actually it would be better to use the action plugin directly instead of the role. It allows you to override all the filenames and all the behavior.
See more here: https://avd.arista.com/devel/docs/plugins/Modules_and_action_plugins/eos_cli_config_gen.html