opschain admin nodes
Included from Basic tier
The node lifecycle lanes — everything that takes a node out of service, or
brings one back. Day-to-day CRUD lives under opschain nodes
(opschain docs cli/nodes); the destructive verbs sit here behind
deliberate admin friction: delete and destroy preview until --confirm,
and destroy only accepts an already-deleted node.
| Subcommand | Purpose |
|---|---|
opschain docs cli/admin-nodes-delete | Soft-delete a node and its subtree — hidden, path reserved, fully reversible. |
opschain docs cli/admin-nodes-restore | The full undo of delete. |
opschain docs cli/admin-nodes-destroy | Permanently remove a soft-deleted subtree's data (events excepted — the audit always persists). |
opschain docs cli/admin-nodes-export | Capture the subtree as one credential-free zip: definitions, run history, events. |
opschain docs cli/admin-nodes-import | Recreate an exported subtree's definitions through the ordinary authorised create lanes. |
The blessed decommission flow is export → delete → destroy: the archive becomes the lasting record, delete takes the subtree out of service reversibly, destroy reclaims the storage once nobody has objected.
Every verb targets a server and authenticates as the ordinary user — there
is no separate admin credential; the server checks read plus the node's
deletable rule action. Node paths are the usual demo,
demo/environments/dev, demo/environments/dev/assets/web shapes, and
every verb works on an entity path too (demo/entities/rack_1): deleting
an entity hides it and its child entities, and restore brings them back.
See also
opschain docs cli/nodes— create, list, show, update.opschain learn 8.1— backup and interchange, guided.