[Feature Request] Support deploying multiple or all environments with a single command

[nosovk]

Describe the solution

Currently, wrangler deploy only allows deploying a single target at a time. In projects with multiple environments defined in wrangler.toml, users must run separate commands for each environment. This is especially cumbersome when environments target different Cloudflare accounts or regional setups.

Use Case: I have a configuration where I need to deploy the same code to multiple accounts/environments simultaneously to keep them in sync.

name = "next-logger"
main = "index.ts"
compatibility_date = "2025-12-26"
account_id = "account1"

[vars]
SERVICE_ACCOUNT_EMAIL = "acc1@mail.com"

[env.account2]
name = "next-logger"
account_id = "account2"

[env.account2.vars]
SERVICE_ACCOUNT_EMAIL = "accoun2@mail.com"

Currently, I have to run:

wrangler deploy (for account1)

wrangler deploy --env account2 (for account2)

Proposed Solution: Add a flag to support deploying all defined environments or a list of specific environments in one command.

Examples:

wrangler deploy --all (Deploys top-level + all [env.x] blocks)

wrangler deploy --env account1,account2 (Deploys a specific comma-separated list)

This would improve developer experience and reduce the complexity of CI/CD scripts.

[MattieTK]

Thanks nosovk for your request. Have you tried using a package.json script that would deploy all these envs at the same time? I'm curious as to what would be better about wrangler deploy --all over something like this.

For example

Using concurrently:

{
  scripts: {
    deploy:staging: wrangler deploy --env staging,
    deploy:production: wrangler deploy --env production,
    deploy:eu: wrangler deploy --env eu,
    deploy:all: concurrently "npm:deploy:staging" "npm:deploy:production" "npm:deploy:eu"
  }
}

Using npm-run-all:

{
  scripts: {
    deploy:staging: wrangler deploy --env staging,
    deploy:production: wrangler deploy --env production,
    deploy:eu: wrangler deploy --env eu,
    deploy:all: npm-run-all --parallel deploy:*
  }
}

Using native shell (no extra deps):

{
  scripts: {
    deploy:all: wrangler deploy --env staging & wrangler deploy --env production & wrangler deploy --env eu & wait
  }
}

[nosovk]

Thanks for the suggestions! We are actually using a similar approach with npm workspaces and the --if-present flag to orchestrate deployments across our monorepo. However, this "user-land" solution has significant drawbacks as the project scales:

Maintenance Overhead: In our case, the number of environments per worker is dynamic and can range from 1 to 20. Hardcoding every environment into package.json scripts for every workspace becomes a maintenance nightmare and is very error-prone.

Dynamic Environments: Our environments aren't always static. When environments are added or removed frequently, we have to manually sync wrangler.toml with package.json scripts, which feels like unnecessary duplication of logic.

CI Efficiency (Build vs Deploy): Currently, running wrangler deploy --env X multiple times triggers a full build/bundle process for each environment. If the only differences are environment variables or the destination Account ID, rebuilding the same code 20 times is a huge waste of CI time and resources.

A native --all or --env e1,e2 flag would allow Wrangler to potentially build once and deploy many, which is much more efficient than spawning multiple independent processes via shell or concurrently.