Deploy worker to multiple zones

[cloudflare]

Deploy worker to multiple zones

[marc-barry]

What I do is the following:

• Use wrangler publish to publish the actual Worker to our account and under the workers.dev domain. When this happens the script is created in our account.
• I then use the API to assign routes for all the zones that need the Worker (i.e. via https://api.cloudflare.com/#worker-routes-create-route).

Like the original poster we also have hundreds of domains which need the exact same script. And the environment concept creates script names with the environment name appended with the exact same content. This eats into our script number quota but also makes it a little difficult to reason about. One disadvantage of reusing the same script for many zones is obviously a bad deploys blast radius is rather large.

My biggest complaint about what I have had to do is I have to separate out the publishing and route deployment in some circumstances and I do wish that Wrangler could cover this use case.

[essensx]

It is possible via UI and API directly, we did this as a workaround until feature is implemented

[petebacondarwin]

Closing in favour of #669 since we have the feature, just haven't documented it.

[c-ameron]

Any update on this? I believe this is possible via the UI?

[macaws]

Is this still something being worked on? The reason that we are using it is we have a domain setup as follows

Production: client.domain.io/api/*
Staging: client.domain.dev/api/*

We decided to purchase these additional domains versus using client.dev.domain.io because Cloudflare does not like multiple layers of subdomains (This gave us issues)

I've seen mentions of a workaround. Ideally I'd love to have two zones in my wrangler.toml, but until then how are people accomplishing this until then?

[threepointone]

Deploying to multiple domains "just works" in wrangler v2. I'm going to move this to the wranglerv2 repo for now, and we'll close it after we have proper docs and do a GA release.