srl-labs
Template startup configs
To allow for rich configuration experience we have to make sure that startup-config files provided in the topology get templated by containerlab using the vars file we support for "templated topologies" feature.
The reason is to enable users to provide startup config files as Go templates which are templated at runtime and thus enabling to create templated configurations.
For starters we are concerned about sros (partial and regular cfgs) and SR Linux configs
Netlab (https://github.com/ipspace/netlab) provides that and more - it has a completely data model driven approach to multi-vendor config generation
Rather than bake everything into Containerlab, I would suggest to leave the configuration templates to other tools
This is for users who don't use netlab or any other configuration tool. This doesn't change any of existing workflows, as config templating is optional.
It's good to have a basic option to do that, but for more advanced use cases I think the user guide could point to projects like Netlab
I think it would be good for the project to establish some boundaries, offering users some pointers for consideration. Not implementing something can be a feature too - I've seen too many projects that try to be everything to everyone