oz0 tenant orphan-pause
Usage and flags for oz0 tenant orphan-pause.
For: Operators and developers looking up a command.
A team that owns routines or inventory items and has no person as a member, or no person as its admin, is orphaned: doctor lists it and the tenant's admins are told. With --days N (1 to 365) its routines also pause once it has been orphaned for N days, with the reason; they never resume by themselves. --days 0 turns it off (the default).
A governance setting: turning it off or lengthening it takes --reason, and with four eyes on, another admin's approval. Without --days it shows the setting.
Usage
oz0 tenant orphan-pause <tenant> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--days | int | pause an orphaned team's routines after this many days (1 to 365); 0 turns it off | |
--decision-ref | string | the decision or case the change follows, such as a case number (at most 200 characters) | |
--reason | string | why, required for every governance change (at most 500 characters; default $OZ0_REASON); the audit log keeps it |
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.