opschain changes approve
Included from Basic tier
opschain changes approve <id|code> [--owner /|/projects/<code>]
Moves a pending record to approved — the baseline tier's approval, by a
holder of update on the owner's change_records_approve rule path, audited
as audit:change_record:approved naming the approving principal. From now
on runs join it. Approving is a human verb: an agent, a service account or
a step's credential is refused by name.
Under an approval policy (packs:change-governance on a PostgreSQL
server, a policy whose subjects include change_record reaching the
record's scope) the command requests the approval instead — a holder of
update on the owner's change_records rule path may — and prints
change record CHG-2026-042 under /projects/web is awaiting approval (checklist <id>) — held by Production CAB; a reviewer approves it with: opschain approvals approve <id>
The record stays pending until the checklist's quorum approves it
(opschain docs cli/approvals-approve); asking again answers the same
request. -o json carries the record with its approval block. A record
no policy reaches is approved as above.
A request raised under an earlier version of its policy is replaced.
When a policy that holds the record has been updated, disabled or deleted
since the open request was raised — or a policy now holds the record that
the request does not name — asking again withdraws that request (reason:
the approval policy changed; audit:change_record:approval_withdrawn and
audit:approvals:withdraw, exactly as opschain approvals withdraw
records them) and raises a fresh one under the policy's current version,
printing first
the approval policy holding CHG-2026-042 changed since request <old-id> was raised — that request is withdrawn and a fresh one opened under the policy's current version
-o json names the replaced request in approval.replaced_request_id. A
request whose quorum is already complete is never replaced. The policy's
version is read from the store, so a policy update on another server is
seen at once. To take a request back without raising a new one, its
requester runs opschain approvals withdraw (opschain docs cli/approvals-withdraw).
A record linked to an ITSM change (opened or linked by a JSM
connection's change mapping — opschain docs integrations-jsm) is
approved by the ITSM: with no approval policy reaching it the command is
refused by name (change record CHG-… is linked to the ITSM change CHG-12: the ITSM approves it); under a policy it requests the policy's approval as
above, and the record moves to approved only when the checklist has
released and the ITSM has approved the change — both must hold. Once
the checklist has released, asking again is refused by name while the
record waits for the ITSM.
Flags
| Flag | Meaning |
|---|---|
--owner <path> | The record's owner, / or /projects/<code> — narrows a code two owners hold; ignored for an id. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Approved. |
| 1 | Refused — not pending, not found, or you may not approve it. |