Is there an alternate approach to
Is there an alternate approach to managing vars/secrets across environments that doesn't put private values in the wrangler.jsonc file (that I'm committing to git) but also doesn't overwrite what has been set on the dashboard every deploy? I have taken to skipping the vars section in the wrangler config, just putting everything in a secret, and using a .dev.vars file for local testing. It means I need to include a .dev.vars.example in the git repo to know what values need set. I feel like I'm missing something obvious here that lets me work local, deploy remote, and not leak secrets in the git repo.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,529Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
