opschain admin nodes delete

Included from Basic tier

opschain admin nodes delete <path> --confirm

Soft-deletes a node and everything beneath it. A tombstone, not a removal: the subtree becomes hidden from every list and route, new work on it is refused, triggers under it stop firing — and the path stays reserved, so nothing can silently take its place. No data is destroyed; opschain admin nodes restore undoes it completely.

Without --confirm the command only previews, after confirming the node exists:

would soft-delete environment /projects/demo/environments/dev (01999a7e-…)
  the node and everything beneath it become hidden; the path stays reserved;
  new work is refused and triggers under it stop firing. Fully reversible with
  `opschain admin nodes restore` — consider `opschain admin nodes export` first.
re-run with --confirm to delete

The server refuses the delete while changes or workflow runs are still active beneath the node, naming them — finish or cancel those first.

Flags

Flag	Meaning
--confirm	Actually delete. Without it the command previews and exits 0.

Exit codes

Code	Meaning
0	Deleted, or previewed.
1	The server refused (active work beneath, missing node, authorisation).
2	Usage error — malformed path, no server target.

Named errors

• expected a node path like demo, demo/environments/dev or /projects/demo/environments/dev/assets/web, got "…"
• nodes operate on a server's estate — pass --server <url> or 'opschain context use <name>'

Both exit 2.

Examples

opschain admin nodes delete demo/environments/dev --confirm
deleted environment /projects/demo/environments/dev — hidden and reserved; `opschain admin nodes restore demo/environments/dev` undoes this

With --confirm and -o json, prints {"deleted": "<path>"}; the preview is always plain text.

See also

• opschain docs cli/admin-nodes-restore — the undo.
• opschain docs cli/admin-nodes-export — capture the archive first.
• opschain docs cli/admin-nodes-destroy — the irreversible second step.