Wrong D1 instance bound after deploying with wrangler.jsonc
Hi all,
I am working on configuring environments for my project and have set up the following wrangler.jsonc for my project:
I have to post as a gist due to discord limit:
https://gist.github.com/olafghanizadeh/a26c5358497034f435968208271fc87f
When I deploy it is the DEV_D1_ID that is bound to my worker and not what is under the environment, in this case production. If I manually change the binding in the Dashboard it binds the correct resource, but whenever I deploy using wrangler build (github) it reverts to the wrong instance. This actually goes for both r2 and d1 on this worker.
I am working on configuring environments for my project and have set up the following wrangler.jsonc for my project:
I have to post as a gist due to discord limit:
https://gist.github.com/olafghanizadeh/a26c5358497034f435968208271fc87f
When I deploy it is the DEV_D1_ID that is bound to my worker and not what is under the environment, in this case production. If I manually change the binding in the Dashboard it binds the correct resource, but whenever I deploy using wrangler build (github) it reverts to the wrong instance. This actually goes for both r2 and d1 on this worker.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
