oz0 tenant egress
For: Operators and developers looking up a command.
Harness sessions, and the jobs an outside event such as a webhook starts, run in sandbox tier 1 on nodes that have it, where the network goes only through the node's egress proxy. The proxy allows the hosts the tenant lists here, the hosts the process's plugin lists (egress in oz0-plugin.yaml) and those its agent lists, and denies the rest; denials show in the job's live stream and in job get.
The verified plugins' tools that reach hosts for a model (ai.oz0/web's fetch, net-diag's probes, cve-triage's OSV lookups) hold themselves to the same lists on every node, sandboxed or not.
A host is a name (api.github.com, on ports 80 and 443), a wildcard (.example.com), name:port, name: or an IP address. Hosts given here replace the list; with none, the list is shown. --clear empties it.
A list that allows anything the tenant's list did not is a reviewed change: it waits as a change request, with what it widens, until a tenant admin approves it (oz0 change approve); --approve approves it at once after printing its delta, when the tenant's review-widening lets you. A narrowing applies at once.
A new entry that reaches a host serving files anyone can publish (a code host's raw files, a package registry, an object store, a paste site) says so on its finding, since a session that may reach it may download and run whatever is there. That is a reason to look, not a verdict: nothing is refused for it, and approving applies it.
Usage
oz0 tenant egress <tenant> [host...] [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--approve | bool | approve the change request a widening makes at once, after printing its delta | |
--clear | bool | empty the tenant's list | |
--decision-ref | string | the decision or case the change follows, such as a case number (at most 200 characters) | |
--json | bool | print JSON instead of a table | |
--reason | string | why, required for every governance change (at most 500 characters; default $OZ0_REASON); the audit log keeps it |
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.