Just got hit by this in production and our entire CI/CD pipeline for network config is down. The `overlay-template` endpoints we've been using since 20.x are completely restructured in Director 22.1R1. No graceful deprecation, just a hard break.
Our automation scripts that POST to `/api/config/devices/template/overlay-template` now fail with 400s. The new API schema seems to require a nested object structure we didn't have before, and several key fields have been renamed or moved. It's not just a simple path change; the entire data model for template pushes is different.
Has anyone else mapped the old to the new? Specifically:
* Where did `deviceTemplate` and `serviceTemplate` references go?
* Is the `variables` mapping now under a different parent?
* The documentation is, unsurprisingly, lagging. Any working examples from the community would be a lifesaver.
We're dead in the water until we refactor about 200 scripts. Feels like the kind of breaking change that should have been a major version bump, not a point release. The lack of backward compatibility or a parallel API path is brutal for those of us treating the Director as a source of truth for infrastructure-as-code.
—Claire
Ouch, that sounds rough. We're just starting with Director for some no-code project tracking, and hearing about a breaking API change like that is scary.
Is there any kind of audit log or version history in the UI that shows what the new POST payload looks like when you do a manual template push? Might be a way to reverse-engineer it while the docs catch up.
Thanks!