How to handle KV / Queue bindings for branch-based preview deployments?
🖥️D1🪣R2🔑KV
Workers🌍Durable Objects
Workers🌍Durable ObjectsHey everyone 
I’m working on branch-based preview environments for a Workers project and trying to figure out the best way to handle bindings like KV, Queues, Hyperdrive, etc.
Our workflow currently looks like this:
*
* When a feature branch is created, we clone our Postgres database for that branch.
* For Postgres this works fine because we can just pass a DATABASE_URL (so we don’t need Hyperdrive).
The challenge is with Workers bindings, since they’re defined statically in
Ideally what I’d love is something like:
* Deploy a preview Worker for a branch
* During that deployment, preview resources get created automatically (KV namespace, Queue, etc.)
* The preview Worker uses those resources
* When the preview is deleted, merged, or promoted, those preview resources get cleaned up automatically
Basically something like ephemeral bindings/resources tied to preview deployments.
Right now it seems the only options are:
* Share preview resources and prefix keys by branch
* Or create resources via CI and update
Is there a recommended pattern for this with Workers today? Or any plans for ephemeral preview resources similar to how preview deployments work in other platforms?
Curious how others are solving this.
Thanks!
I’m working on branch-based preview environments for a Workers project and trying to figure out the best way to handle bindings like KV, Queues, Hyperdrive, etc.
Our workflow currently looks like this:
*
devdev-feature-branch* When a feature branch is created, we clone our Postgres database for that branch.
* For Postgres this works fine because we can just pass a DATABASE_URL (so we don’t need Hyperdrive).
The challenge is with Workers bindings, since they’re defined statically in
wrangler.jsoncIdeally what I’d love is something like:
* Deploy a preview Worker for a branch
* During that deployment, preview resources get created automatically (KV namespace, Queue, etc.)
* The preview Worker uses those resources
* When the preview is deleted, merged, or promoted, those preview resources get cleaned up automatically
Basically something like ephemeral bindings/resources tied to preview deployments.
Right now it seems the only options are:
* Share preview resources and prefix keys by branch
* Or create resources via CI and update
wrangler.jsoncIs there a recommended pattern for this with Workers today? Or any plans for ephemeral preview resources similar to how preview deployments work in other platforms?
Curious how others are solving this.
Thanks!
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
87,353Members
Resources
Similar Threads
Was this page helpful?
