Did you find a good way of doing this?
Right now our workaround is to fetch the composite and then grab the templates from the composite before forlooping through deploying the individual templates...
Things we have observed that make this workaround ineffective:
- If we run a template that has a macro in it the macro doesn't seem to write to startup even though subsequent templates are writen to startup (superwierd... i suspect it is a NetConf thing... we are going to troubleshoot this but haven't gotten to it yet.)
- We can't use system-variables (as far as we can see by inspecting the frontend the frontend seems to execute javascripts to populate the system variables before deploying. These scripts does not seem to run when deploying a template through API, meaning any system-variables in our templates are empty strings when deployed by API).
- The "template provision status" field in inventory doesn't seem to update correctly. When deploying through API we check the responsebody attributes "Endtime" and "isError" to make sure the deployment of the template is actually done correctly. We haven't had the time to troubleshoot why the template sometimes isn't added to "template provision status" even though DNAC API has responded with "'isError': False".
Best Regards
/Mikael Lindgren
Tele2 Business AB
Umeå, Sweden