Commit DNA Center configuration template after update via API

[BenEa]

Hello,

I want to manage the lifecycle of my configuration templates through GitHub and have them sync with different DNA Center instances through the use of dynamic runners.

I have the same issue with both the terraform provider, and the Python dnacentersdk library.

I can update or create the template into the different DNA Center instances, but I cannot commit them.  There doesn´t seem to be a parameter to commit these templates via API.

Does someone know if this can be acheived?

Thanks!

DNA Center 2.3.3.4.72142

Python SDK:

https://dnacentersdk.readthedocs.io/en/latest/api/api.html#configuration-templates-2-3-3-0:~:text=configuration_archive-,configuration_templates,-device_onboarding_pnp

Terraform:

https://registry.terraform.io/providers/cisco-en-programmability/dnacenter/latest/docs/resources/configuration_template

[Andrea Testino · Accepted solution]

Hi there!

Have you tried setting the "version" parameter when using create_template or update_template when using the PythonSDK or when using the Terraform "dnacenter_configuration_template" resource? 

That should mark the template as committed and allow you to use it to deploy to devices.

The Template Management API doc shows the process (without using the PythonSDK or Terraform, though, the idea should be the same.)

I don't have a DNAC handy right now but let me know if that doesn't work and I can tinker with it this week.

[BenEa]

Thanks Andrea, with the python SDK .configuration_templates.version_template worked!  I couldn´t get it to work with the Terraform provider, I will stay with python on this one.

[Andrea Testino]

Awesome! Love to hear it.