Hey Fred,
another issue I've found when I try to applyconfiglet to device, it prepends configlet to the list of existing configlets, which, my case, breaks the validation since it validates them in a reverse order. How about we update your repo to match the cvprac where they first list all configlets assigned to device and the append the new ones to the bottom of that list.
btw, i'm not sure what's the story with a different API calls - /ztp/addTempAction.do in your case and /provisioning/addTempAction.do in cvprac, but would be good to fix that as well.
@networkop Makes sense to append rather than prepend configlets.
As far as the zpi calls, that is a legacy endpoint due to the version of CVP I was dealing with initially. We can swap out ztp for provisioning
Hey Fred, another issue I've found when I try to applyconfiglet to device, it prepends configlet to the list of existing configlets, which, my case, breaks the validation since it validates them in a reverse order. How about we update your repo to match the cvprac where they first list all configlets assigned to device and the append the new ones to the bottom of that list. btw, i'm not sure what's the story with a different API calls - /ztp/addTempAction.do in your case and /provisioning/addTempAction.do in cvprac, but would be good to fix that as well.