oz0 plugin remove
For: Operators and developers looking up a command.
Uninstall a plugin; nodes stop it and delete it. The removal is refused while anything depends on the plugin (other plugins' grants or uses:, routines, other plugins' flows, running jobs, its records), and the refusal lists them with their owners (oz0 plugin dependents shows the same). Retire it first so nothing new starts to use it, or remove it anyway with --force and a --reason, which the audit log keeps with the list; running jobs are then cancelled.
What named its agents and flows is listed as they go: API key scopes and agent grants marked, routines paused, keep-for rules and legal bases dropped, rules to edit.
Removing a set removes, newest first, the members it installed that nothing else uses (no other plugin's grant or uses:, no other set), each checked and audited as a removal that names the set; a member that was installed before the set, or that something uses, stays, and the answer says why.
Usage
oz0 plugin remove <name> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--force | bool | remove it although others depend on it (takes --reason) | |
--reason | string | why a forced removal goes past its dependents (at most 500 characters; default $OZ0_REASON) | |
--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.