Skip to main content
Version: v5.7.0

opschain properties history

Included from Basic tier

opschain properties history <node-path> [--limit N]

Lists a server node's stored properties versions, newest first — version numbers and creation times only (the listing excludes the document data; use opschain properties show with its version flag to read one). Server-only: pass --server <url> or select a context with opschain context use.

Flags​

FlagMeaning
--limit NMaximum versions to list (server default 1000).
--filter <column>[!]=<value>Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased (spaces/dashes fold to _); * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. Applied client-side within the returned page (--limit). Grammar: opschain docs cli.

Output​

opschain properties history demo/environments/dev
VERSION CREATED
4 2026-10-01T03:12:45Z
3 2026-09-28T22:05:11Z

When the server truncated the listing, a trailing note says more versions exist — raise --limit to list them. With -o json / -o yaml, an array of documents with path, id and version fields (plus created_at where the server reports it).

Exit codes​

CodeMeaning
0Listed (no versions prints a note and still exits 0).
1The node does not exist, 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.

See also​

  • opschain docs cli/properties-show — read one version's data.
  • opschain docs cli/properties-edit — every edit lands here as a new version.