oz0 tenant cors

Usage and flags for oz0 tenant cors.

For: Operators and developers looking up a command.

By default no page on another origin may read the tenant's job and feed events (GET /v1/jobs/{id}/events, GET /v1/feeds/{feed}/events) or ask for stream tickets: browsers refuse them, and the edge refuses the request. Each --allow-origin names one origin exactly as browsers send it (scheme, host, and port when it is not the default; https, or http on localhost for development; no path and no wildcard), and the list replaces the tenant's.

Such a page reads with a one-time stream ticket or an app's key, never a person's session: the answer never allows credentials. Allowing an origin widens who can read, so it takes --reason; --clear and removing origins do not. Admins of the tenant may change it; each change is audited (tenant.cors), and edges apply it within seconds.

Usage

oz0 tenant cors <tenant> --allow-origin https://app.example.com [--allow-origin ...] --reason <why> | --clear [flags]

Flags

FlagTypeDefaultDescription
--allow-originstringArrayan origin whose pages may read the tenant's streams (repeat for more)
--clearboolallow no other origin (the default)
--decision-refstringthe decision or case the change follows, such as a case number (at most 200 characters)
--jsonboolprint JSON instead of a table
--reasonstringwhy, required for every change (default $OZ0_REASON); the audit log keeps it

Inherited flags

FlagTypeDefaultDescription
--contextstring$OZ0_CONTEXT or <config dir>/orchestrator-zero/context.jsonCLI context file written by server init
--log-levelstringinfolog level: debug, info, warn or error

See all oz0 commands and the global flags.

On this page
Copyright © 2026