Update a node to its catalog's current version
POST/api/update_node_from_template/:project_guid/:workflow_guid/:node_guid
Re-materializes a linked node from a version of its catalog adapter, carrying its config values across.
Defaults to the version the catalog's checkout holds. Naming an older
commit moves the node back to that version, which is a real action
rather than a repair: the version a node should be on is a per-node
decision, while pulling the catalog is instance-wide.
Gated on Edit config fields: an update can add, remove, and redefine the node's config fields, which is the same authority editing them by hand takes - the difference is only that the vendor decided the shape rather than the operator.
Request
Responses
- 200
- 400
- 404
- 409
- 422
Successful Response
The node does not follow a catalog
Project, workflow, or node not found, or the catalog no longer provides the template
The node is running, or the new version pins a library this project can't have
Validation Error