render-cli deploys create: Trigger Render Deploys
render deploys create <service-id> triggers a new deploy of a Render service from the Render CLI, optionally waiting until it completes.
Render builds on git push, but the CLI lets a pipeline trigger and watch a deploy explicitly. It authenticates with a workspace API key.
What it does
render deploys create SERVICE_ID starts a new deploy of the named service. --wait blocks until the deploy reaches a terminal state. render services list finds the service id, and --output json/--confirm make the CLI scriptable and non-interactive.
Common usage
# API key authenticates the CLI in CI
export RENDER_API_KEY=rnd_xxx
render deploys create srv-xxxxxxxxxxxx --output json --confirm --waitOptions
| Command / flag | What it does |
|---|---|
| deploys create <service-id> | Trigger a new deploy |
| --wait | Block until the deploy finishes |
| --output json | Machine-readable output for scripting |
| --confirm | Skip interactive confirmation |
| services list | List services to find the id |
| RENDER_API_KEY | API key for non-interactive auth |
In CI
Set RENDER_API_KEY (a workspace API key) so the CLI does not enter its interactive login/TUI. Add --output json and --confirm so it never opens the interactive picker, and --wait so the job fails when the deploy fails.
Common errors in CI
"Error: RENDER_API_KEY ... is not set" (or an interactive login prompt) means no API key in the environment. "401 Unauthorized" means an invalid or revoked key. A command that hangs is the interactive TUI; add --output json and --confirm to force non-interactive mode.