Move chosen nodes onto a newer release of their catalog adapter
POST/api/update_nodes_from_template
Applies an adapter update to each named node, one node at a time.
Each node is its own commit, because each is its own change: the config merge an update performs is per-node, and a single commit covering twenty of them could not be reverted for one. This is the difference from a library upgrade, which copies identical files into every node and so commits once.
Failures are per node and never stop the batch. update_node_from_template
raises for a node that is running, has been unlinked, or whose catalog has
gone; here each of those is one row in skipped and the loop continues.
Request
Responses
- 200
- 400
- 403
- 422
- 503
Successful Response
No nodes named
Not a collaborator on the project
Validation Error
The runtime could not be reached, so no node could be checked for being active