oz0 changes approve
For: Operators and developers looking up a command.
Approve a job's changeset, bound to its patch's digest, so it is applied.
It decides the job's waiting changes approval with the digest of the apply call's arguments, which name the patch by its digest, so a decision is bound to those arguments: the job refuses the decision for any other patch. With --patch (the digest oz0 changes show prints), it decides only when the waiting approval is for that patch, the one you reviewed; without it, it says which patch it decided.
A changeset that touches a plugin's tests or rules then waits for its second approval, which this command decides too: only a person signed in with governance.write who neither started the job nor approved its changes may approve it.
Usage
oz0 changes approve <job> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--comment | string | why; the job's agent and history keep it | |
--patch | string | sha256:<hex> of the patch you reviewed (oz0 changes show prints it); refuse any other | |
--tenant | string | default | tenant |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.