oz0 subject rule
For: Operators and developers looking up a command.
A mapping rule names the data subjects of the jobs a trigger starts, from what the trigger carries: for a webhook, its JSON body; for an event source, {body, event}: the delivery's body and the event its source's function made of it (none yet for the delivery's own job, so point into /body); for a routine, {input, body}: the job's input and what fired it; for a channel binding, the message ({text, room, workspace}) and identity: the author's {id, name, account}.
Each of up to 8 expressions is a JSON pointer (--pointer /buyer/email) or a CEL expression (--cel 'payload.items.map(i, i.owner)'), yielding a string or a list of strings; the union, at most 8 subjects, are the job's. A scheduled routine fire has no payload and gets none. Try a rule with subject rule test on a sample before you set it.
Usage
oz0 subject rule [command]
Subcommands
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.