Workers KV bindings get removed on deploy + project name mismatch (Git integration, no wrangler.toml
🔑KVWranglerWorkers✅Solved
I’m using Cloudflare Workers with a Nuxt project via the Git integration(CI/CD in Cloudflare). Because of that, I currently don’t have a
wrangler.toml
wrangler.toml
in my repo.
I’m running into two related issues:
1. Workers KV bindings * I add a KV binding in the Cloudflare dashboard. * After the next deployment, the binding is gone again. * I want to use KV for things like rate limiting, but every deploy breaks this. * It feels like some config is being overwritten, but I don’t know from where. 2. Project / Worker name mismatch * I’m getting warnings in the console/logs about a different project/worker name. * I’d like to rename this properly to avoid noise and false-positive warnings. * Without knowing where the “source of truth” config lives, I’m unsure how to fix this cleanly.
What I’m trying to figure out: * Where is the actual Worker configuration stored when using Git integration? * Is there a way to export or sync the current config(bindings, name, etc.) into my repo? * Is it safe to add a
wrangler.toml
wrangler.toml
now, or would that override/break the existing setup? * What’s the recommended way to manage KV bindings persistently with Git-based deployments?
Any pointers or best practices would be appreciated.