oz0 setting
For: Operators and developers looking up a command.
Settings are what plugins declare under requires.settings: addresses, backends' names, switches. They are stored and shown as they are and are never scanned for as secrets, so a key, a token or a password is refused: keep those as secrets (oz0 secret set). Admins set and delete settings; operators and admins list them.
A setting that loosens a safety control is a governance setting: GUARDRAILS_CLASSIFIED_LOCAL, the classified markings the guardrails let into agents whose data stays on the node, and GUARDRAILS_CONFIG, the guardrails' checks (turning one off, such as the command guard, loosens). Setting or deleting one takes --reason (or $OZ0_REASON) and the governance.write permission, and a loosening waits for a second admin where the tenant has four eyes on.
Usage
oz0 setting [command]
Subcommands
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--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.