Replies: 2 comments
-
|
Totally agree with you -- we need to restructure the current way of dealing with provider-specific settings. It would be best to move everything under devices.device, for example devices.srlinux.clab. group_vars could go there as well as provider-specific node attributes which would then be specified in providers.p.attributes.node, for example: Provider-specific settings would then (according to your idea) go into node.provider dictionary, for example nodes.r1.clab.kind. I missing something? If not I could whip this up pretty soon. |
Beta Was this translation helpful? Give feedback.
-
|
Implemented a long time ago |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For example, on Containerlab we have provider_kind which gets copied to node.kind
Instead, each provider could declare attributes:
and then those would be copied to node.<provider>.xxx:
and referenced in templates as {{ clab.kind }}, etc.
Beta Was this translation helpful? Give feedback.
All reactions