Skip to main content
Create a root key with the permissions listed on this page under Root Keys in the dashboard sidebar. CLI commands can instead use a session from unkey login with the required permissions. See Permission reference for every permission.
Promote a deployment so it becomes the current deployment of its production . The live domains move to it, and the previous deployment stops after 30 minutes on standby. The deployment must be ready, in the production environment, and not shutting down, and its must already have a current deployment. You can’t promote the deployment that’s already current, except after a rollback. Then promoting it ends the rolled-back state and turns automatic promotion back on. The command returns right away. Poll unkey deployments get or unkey deployments list for the result. Promoting needs an active Compute plan. Without one the API answers 412 with The workspace has no active Compute plan. A workspace over its Compute spend cap gets The workspace is suspended by its Compute spend cap. Raise the spend limit to resume. See Compute plans.

Usage

Flags

string
required
ID of the deployment to promote.

Shared flags

Every resource command accepts these; CLI output and shared flags describes them in full.
string
A JSON document sent as the request body instead of building it from the flags above. It is mutually exclusive with the request-building flags, and unknown fields are rejected locally. See Send a raw body.
string
Root key used for the request. Falls back to UNKEY_ROOT_KEY, then stored credentials, including a CLI session. See CLI authentication for the full precedence order.
string
default:"https://api.unkey.com"
Base URL of the API. Falls back to UNKEY_API_BASE_URL. You don’t normally need to set it.
string
default:"~/.unkey/config.toml"
Path of the TOML config file. Falls back to UNKEY_CONFIG. An explicit --config takes precedence over a stored CLI session. Browser login stores a session, not a root key in this file. See CLI authentication.
enum
default:"human"
Use human (default) for name-first summary tables and single-response trees, or json for the unchanged full response envelope, including all fields and pagination. Trees wrap long values without truncation. Terminal tables use relative timestamps and may shorten display names and descriptions, but never identifiers, slugs, or credentials. Redirected human output keeps complete values and uses RFC3339 UTC timestamps. Falls back to UNKEY_OUTPUT; other values are rejected. --json also selects JSON output. Add --debug to print the request ID to stderr. See Output formats.
boolean
Print the successful response’s request ID to stderr, separate from stdout.
boolean
Print the full response as JSON. Takes precedence over a valid --output or UNKEY_OUTPUT value.

Required permissions

Your root key needs write on the environment:
  • unkey:v1:<workspace_id>:projects/<project_id>/apps/<app_id>/environments/<environment_id>#write
If the deployment doesn’t exist or your key doesn’t have the permission, you get the same 404: The requested deployment does not exist. If your key can read the deployment, you get a 403 that names the missing permission instead. See Root key permissions for the full catalog.

Examples

Promote a deployment:
Send the request body as JSON:

API endpoint

The command calls POST /v2/deployments.promoteDeployment and prints its response. The request fields carry the same names as the flags in camelCase, which is the shape --body expects.

Production and preview

What promote and rollback change and when traffic switches.
Last modified on October 28, 2026