Skip to main content
Version: v5.8.0

opschain changes list

Included from Basic tier

opschain changes list [--owner /|/projects/<code>] [--state pending|approved|closed] [--code <code>] [--scope-holds <path>] [--limit <n>]

Lists change records newest first. A record under an owner you cannot read never appears.

The STATE column reads approved (held) for an approved record whose ITSM approval was withdrawn (a JSM-linked record on the PostgreSQL store): it is still approved — --state approved lists it — but no new run joins it until the ITSM approves it again (opschain changes show names the reason).

--scope-holds keeps the records whose scope holds a target — the test a run's join uses. Give a node path, or, against a server, a workflow path /projects/<code>/workflows/<code>: the workflow is tested by the one node every change step of its latest published version targets, else its project. With --state approved it lists the records a run on the target may join:

opschain changes list --state approved --scope-holds /projects/web/environments/prod/assets/gateway

The local lane takes node paths only; a workflow path there is refused by name.

Flags​

FlagMeaning
--owner <path>Only records owned by exactly this path.
--state <state>Only pending, approved or closed records — there are no other states.
--code <code>Only records with this code.
--scope-holds <path>Only records whose scope holds this node path — or, on a server, this workflow path's effective target.
--limit <n>At most this many records (default 100).

Exit codes​

CodeMeaning
0Listed (possibly none).
2Usage error — an unknown state, a non-positive limit, a workflow path to --scope-holds in the local lane.