oz0 plugin config rollback
File the inverse of an applied plugin_config change request as a new one: every part it changed, back to what it found, compared with the plugin as it is now.
For: Operators and developers looking up a command.
File the inverse of an applied plugin_config change request as a new one: every part it changed, back to what it found, compared with the plugin as it is now. It is approved as any configuration change is (oz0 change approve), and a part it widens again, such as a function the change refused, is a loosening another admin approves. Takes changes.review and each part's own permission.
Usage
oz0 plugin config rollback <change-id> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--approve | bool | approve the change request at once, when you may | |
--decision-ref | string | the decision or case the change follows, such as a case number (at most 200 characters) | |
--dry-run | bool | show what the rollback changes, and file nothing | |
--json | bool | print JSON instead of a table | |
--reason | string | why, required for every governance change (at most 500 characters; default $OZ0_REASON); the audit log keeps it | |
--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.