opschain admin nodes destroy

Included from Basic tier

opschain admin nodes destroy <path> --confirm

The second, irreversible step of decommissioning: permanently removes every stored row beneath a node that was already soft-deleted — changes, runs, steps, documents, artifacts (blobs released), templates, remotes, triggers, windows. The events table is never touched, so the audit trail and chain views survive the destroy. A node that has not been soft-deleted first is refused by the server; the blessed order is export → delete → destroy (opschain docs cli/admin-nodes).

Without --confirm the command fetches and prints the per-type manifest of what would be removed:

would destroy /projects/demo and every row beneath it (events excepted — the audit persists):
  changes                  214
  nodes                    7
  steps                    1931
  …
re-run with --confirm to destroy permanently

Zero counts are omitted; a note: line appears when the server attaches one. With --confirm the same manifest prints under destroyed <path> — removed: followed by events were not touched; the audit trail persists.

Flags

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

Exit codes

Code	Meaning
0	Destroyed, or previewed.
1	The server refused (node not soft-deleted, missing, 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 destroy demo
opschain admin nodes destroy demo --confirm

-o json / -o yaml print the manifest document (path, destroyed, counts, note) for the preview and the destroy alike.

See also

• opschain docs cli/admin-nodes-export — the lasting record; take it before destroying.
• opschain docs cli/admin-nodes-delete — the required first step.