oz0 subject
For: Operators and developers looking up a command.
A job started with data subjects (run --data-subject, data_subject and data_subjects in the runtime API, or a trigger's mapping rule: subject rule) has its payloads encrypted with a key of its own, wrapped by a key of each person's.
subject find lists what a tenant holds about the person and what keeps each job; subject erase destroys the keys, so the payloads in Temporal's history, in External Storage and in backups of either can no longer be read, redacts the audit entries about the person, and deletes the person's jobs from Temporal; jobs of an agent with a keep_for period wait for it (retention keep-for).
The tenant's erasure policy (tenant erasure-policy) may have a second admin approve an erasure, or refuse it. The subject itself is never stored, only its hash.
Usage
oz0 subject [command]
Subcommands
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--tenant | string | default | the 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.