Skip to main content
Version: v5.7.0

opschain nodes

Included from Basic tierassets

The estate CRUD family: projects, environments, assets and entities, 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.

SubcommandPurpose
opschain docs cli/nodes-listList the estate tree, or the subtree under a node path.
opschain docs cli/nodes-showShow one node's details.
opschain docs cli/nodes-createCreate a project, environment, asset or entity at a node path.
opschain docs cli/nodes-updateUpdate 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 project demo (the projects/ 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 a project,
  • demo/entities/rack_1, demo/environments/dev/assets/web/entities/orders_db/entities/orders_schema — an entity, under any node and nested to any depth,
  • /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; entities live under any node, and nothing but entities lives under an entity. A path outside those shapes fails with expected a node path like demo, demo/environments/dev, /projects/demo/environments/dev/assets/web or demo/entities/rack_1, got "…" (exit 2), and a non-server target with nodes operate on a server's estate — pass --server <url> or 'opschain context use <name>'.

The same path grammar addresses an entity in opschain properties and opschain settings (show, edit, history) and in the opschain admin nodes lifecycle verbs. Verbs with no meaning on an entity — creating a change, assigning a template version, storing or reading artifacts — refuse an entity path by name before calling the server.

See also​

  • opschain docs cli/admin-nodes — the lifecycle lanes: delete, restore, destroy, export, import.
  • opschain learn 1.1 — the estate, guided.