You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You do realize that you do not need to assign config templates to the device to be able to use them. They can be "not assigned" and you can still include them / use them in the devices. We demonstrated this in the Freeform Labs in cloudlabs.
If you still need it, please explain the use case in detail for us. (Maybe you want to use specific config template for specific devices? in that case you could just name the CT on a per device basis and include them via a %include <devicename_ct.jinja> %)
Yes, i need for this feature. I now in cloudlab explain how to use template, but after we create individule or global template jinja this need assign to assosiate device intenal system to rendering config. In my case, create name ‘junos_configuration.jinja’ the file include all config to deliver configuration CRB config IP Fabric.
Hi,
Currntly terrafrom provider not already assignment config template to system.
if i check in api apstra this example :
SSXOei_RYGUEpTDeAKg : this system id
j0LBK2RzArOx5ulaT6A : this id for template.
if see on apstra freefrom UI, after import device from terrafrom by default config template not assigment:
our use case terraform can be assign template also to device system internal
The text was updated successfully, but these errors were encountered: