oz0 approval decide
For: Operators and developers looking up a command.
Say what became of a write whose outcome is unknown: a call of a function that is not retry-safe ran out of time, lost its node, or ended with an error the platform cannot read after its request may have reached the tool, so nobody knows whether it wrote. The job waits for a person (an approval of kind unknown_outcome) when on_unknown says wait, which by default it does for a job a person started.
Check the system the tool writes to, then answer:
happened the job goes on, and the agent reads that the write is taken as done; there is no result to read. run_again the call runs once more under the same idempotency key: a server that honours the key does nothing new, but one that does not may write a second time (the approval's card and approval list say which). When the call's node was lost, the call runs again on that node, the job's home, so it waits until the node is back, as the job's next calls do; stop the job if the node will not come back. stop the job fails with the failure kind unknown_outcome. Denying the approval does the same.
It is decided by those who decide a tool approval of the same function, with four eyes where they say so. The decision names the digest of the arguments it decides on (--args-sha256), read from approval list without the flag.
Usage
oz0 approval decide JOB APPROVAL happened|run_again|stop [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--args-sha256 | string | the approval's, from approval list | the digest of the arguments you decide on |
--comment | string | why; the agent sees it, and so does the job's history | |
--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.