Maintenance plan and approval API

Creates a draft maintenance plan for the selected nodes.

Send name, node_ids, steps, concurrency, and an optional execution window. Steps are named actions supported by the plan schema, such as cordon, drain, patch, validate, and uncordon. concurrency defaults to 1 and must be a positive integer permitted by organization policy.

To create a drain-and-patch plan for 2 selected nodes, send:

{
  "name": "eu-west security rollout",
  "node_ids": ["nod_eu01", "nod_eu02"],
  "steps": [
    { "type": "cordon" },
    { "type": "drain" },
    { "type": "patch", "patch_policy_id": "patch_security" },
    { "type": "validate" },
    { "type": "uncordon" }
  ],
  "concurrency": 1,
  "failure_policy": "pause"
}

Returns 201 with draft ID and revision. failure_policy defaults to pause and can be continue only where organization policy permits it. Unsupported step sequences return 422 invalid_plan.

Returns the target digest, capacity and storage blockers, and approval requirements. It does not reserve future destinations.

Records approval for the reviewed plan revision.

Requires maintenance:approve, If-Match, a preflight_id, and a reason. It records an approval for that revision. Self-approval returns 403 self_approval_forbidden under the default policy. A changed target set returns 412 plan_stale.

Starts an approved maintenance plan.

Requires maintenance:write, If-Match, and an idempotency key. Valid admission returns 202 with parent operation ID. Missing or expired approval returns 409 approval_required.

Execution repeats required checks before each disruptive step. A valid approval does not bypass insufficient capacity or unresolved storage ownership.

Stops admission of new node sequences. Running children resolve according to their lifecycle.

Resumes maintenance within the reviewed revision and approval window.

Requires the same reviewed revision and a valid approval window; otherwise new review is needed.

Read the plan for per-node step outcomes and the Operation API for active children. Successful moves or patches are not rolled back when another target fails. See maintenance approvals for revocation and exceptions.