opschain approvals set-metadata
packs:change-governance
opschain approvals set-metadata <run-id> [--owner <who>] [--category standard|normal|emergency] [--ref <system>:<record-type>:<id>[:<relationship>]]... [--clear-refs]
Writes a subject's governance block
(ChangeGovernanceService.SetGovernanceMetadata): the change owner
(defaults to the requester; zero authz powers), the change category, and
the typed external references. The block is mutable through the whole
lifecycle, audited with before/after, and never fingerprinted. Writable
by the requester, the change owner, or a principal with update on the
target. Supplied --refs replace the stored set; --clear-refs replaces
it with the empty set. Record types: change, incident, issue, problem,
release, request, task; relationships: implements, resolves, caused,
relates_to. A reference URL is not settable here — use opschain api v2 call ChangeGovernanceService/SetGovernanceMetadata when one is needed.
-o json / -o yaml emit the updated governance block.
Flags
| Flag | Meaning |
|---|---|
--owner <who> | The change owner. |
--category <category> | standard, normal or emergency. |
--ref <system>:<record-type>:<id>[:<relationship>] | A typed external reference, e.g. JSM:change:CHG-42:implements (repeatable). |
--clear-refs | Replace the stored external references with the empty set. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | The governance block was updated. |
| 1 | Refused — not the requester/owner and no update on the target, an unknown run, or an invalid category/reference vocabulary (named by the server). |
| 2 | Usage error — nothing to write, a malformed --ref, --clear-refs with --ref, or a missing server target. |