Skip to main content
Version: v5.7.0

opschain properties show

Included from Basic tier

opschain properties show <node-path> [--version N]

Shows a server node's stored properties document — the current version, or with --version N one version from its history. The node path is the usual positional form (demo, demo/environments/dev, demo/environments/dev/assets/web, an entity such as demo/entities/rack_1, or a full /projects/... path). The current version reads over the API v2 by-path document read (PropertiesService.GetProperties); a --version read resolves the document through the node's properties relationship and reads the v1 versions endpoint, which has no v2 twin yet. Server-only: pass --server <url> or select a context with opschain context use.

Flags​

FlagMeaning
--version NShow this version from the document's history instead of the current one.

Output​

opschain properties show demo/environments/dev
path: demo/environments/dev
id: 01999a7e-…
version: 4
created_at: 2026-10-01T03:12:45Z
data:
{
"opschain": {
"env": {
"REGION": "ap-southeast-2"
}
}
}

With -o json / -o yaml, a document with path, id, version, created_at and data fields.

Exit codes​

CodeMeaning
0Shown.
1The node or version does not exist, the node has no stored document, or the request failed.
2Usage error.

Named errors​

  • stored properties documents live on a server's nodes — pass --server <url> or 'opschain context use <name>' (exit 2).
  • <node-path> has no stored properties document on this server.
  • expected a node path like demo, demo/environments/dev, /projects/demo/environments/dev/assets/web or demo/entities/rack_1, got "<arg>" (exit 2).

See also​

  • opschain docs cli/properties-history — which versions exist.
  • opschain docs cli/properties-edit — write a new version.
  • opschain learn 1.3 — properties and settings, guided.