As a user, I want to initiate a node sync using the REST API on the child node.
As a user, I want to initiate a node sync using the REST API on the node. This supports cases where no agent exists on the node.
- Add a new API endpoint: /v2/nodes/<node_id>/actions/sync/
- Move node sync functionality in the node (agent) handler into the platform.
- The node handler will call the new API and return the result in a manner that ensure backwards compatibility.
Updated by mhrivnak over 7 years ago
If this call is made, the receiving process is by definition on the child node, right? If so, the node_id is implicit and doesn't need to be part of the resource identifier.
This is an implementation detail, but I'm interested in considering something like "/v2/child_node/actions/sync/"