opschain nodes
Included from Basic tierassets
The estate CRUD family: projects, environments and assets, read and written
on a server. Nodes are server estate with no local form — every verb needs a
target (--server <url>, OPSCHAIN_SERVER, or the active
opschain context) and fails with a usage error without one.
| Subcommand | Purpose |
|---|---|
opschain docs cli/nodes-list | List the estate tree, or the subtree under a node path. |
opschain docs cli/nodes-show | Show one node's details. |
opschain docs cli/nodes-create | Create a project, environment or asset at a node path. |
opschain docs cli/nodes-update | Update a node's attributes (code is immutable). |
Deletion is deliberately absent here: soft delete, restore, permanent
destroy and the export/import archive lanes live behind admin friction
under opschain admin nodes (opschain docs cli/admin-nodes).
Node paths
Every verb addresses its node with the same positional path:
demo— the projectdemo(theprojects/prefix is implied),demo/environments/dev— an environment under a project,demo/environments/dev/assets/web— an asset under an environment,demo/assets/shared— an asset directly under an Enterprise project,/projects/demo/environments/dev— the full form passes through unchanged.
The hierarchy is enforced while parsing: environments live under projects
only; assets live under environments, or directly under an Enterprise
project. A path outside those shapes fails with
expected a node path like demo, demo/environments/dev or /projects/demo/environments/dev/assets/web, got "…"
(exit 2), and a non-server target with
nodes operate on a server's estate — pass --server <url> or 'opschain context use <name>'.
See also
opschain docs cli/admin-nodes— the lifecycle lanes: delete, restore, destroy, export, import.opschain learn 1.1— the estate, guided.