oz0 tenant move
For: Operators and developers looking up a command.
Move a tenant to another of the cluster's Temporal backends (tenant backends lists them; the edges' --temporal-backends-file names them). Once an edge finds the tenant's namespace ready on the new backend, new jobs, schedules and routines start there, while the jobs that run finish on the old one: nodes run workers against both through the edge, and never learn which backends they are. Job IDs and lookups find a job on either backend.
The move ends when nothing runs on the old backend any more. --namespace names the tenant's namespace on the new backend, such as an existing Temporal Cloud namespace <name>.<account>. Without a backend it shows the tenant's backend and its last move; --cancel cancels a move before it ends, which moves the tenant back: new jobs start on the old backend again, and those that started on the new one finish there.
A move ends at its --deadline (default 168h) even with jobs still on the old backend: they keep running there, with their workers, and stay reachable, while the tenant's new work stays on the new backend; without a backend, --deadline or --no-deadline changes the deadline of the move that runs, from now.
Usage
oz0 tenant move <tenant> [backend] [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--cancel | bool | cancel the tenant's move before it ends, which moves it back | |
--deadline | duration | 168h0m0s | end the move after this long even with jobs still on the old backend, which finish there; without a backend: the running move's new deadline, from now |
--json | bool | print JSON instead of a table | |
--namespace | string | its default name there | the tenant's namespace on the new backend |
--no-deadline | bool | the move ends only when nothing runs on the old backend | |
--wait | duration | wait up to this long for the move to end, as when nothing runs on the old backend |
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.