oz0 incident regimes
For: Operators and developers looking up a command.
Show the tenant's incident regimes: each one's stages with their deadlines and what they count from, its severities, and when reminders go out before a deadline. The built-in regimes are defaults to be confirmed: which apply to you, and when their clocks start, is your lawyer's call, and you change them here.
--file sets them from a JSON file ({"regimes": [{"name", "label", "basis": "awareness"|"classification", "stages": [{"name", "after": "72h", "from"}]}], "severities": [...], "remind_before": ["24h", ...]}); --defaults goes back to the built-in ones. It is a governance setting (incident_regimes): removing a regime or a stage, a longer stage, a later start or a dropped reminder loosens it, and waits for a second admin where four eyes is on. Open incidents keep the regimes they were given.
Usage
oz0 incident regimes [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--decision-ref | string | the decision or case the change follows (at most 200 characters) | |
--defaults | bool | go back to the built-in regimes | |
--file | string | set the regimes from this JSON file | |
--json | bool | print JSON instead of a table | |
--reason | string | why, when setting (required; default $OZ0_REASON) |
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 |
--tenant | string | default | the tenant |
See all oz0 commands and the global flags.