oz0 subject rule test
Try a trigger's mapping rule, or the one given with --pointer and --cel, on a sample: it changes nothing
For: Operators and developers looking up a command.
Try a trigger's mapping rule, or the one given with --pointer and --cel, on a sample: it changes nothing
Usage
oz0 subject rule test KIND NAME --payload FILE [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--cel | stringArray | a CEL expression over payload (and identity for a channel), such as payload.cc (repeatable) | |
--identity | string | for a channel: a file with the author's identity as JSON ({id, name, account}) | |
--json | bool | print JSON instead of a table | |
--payload | string | a file with the sample payload as JSON, or - for standard input | |
--pointer | stringArray | a JSON pointer into the payload, such as /buyer/email (repeatable) |
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.