Update Environment vars using the API while still using wrangler for dev & deploy
I have a worker which is created/developed just using the normal wrangler stuff (commands and wrangler.toml). The worker has some environment variables (plain_text) which get updated by an external tool using the Cloudflare API - that works fine.
However every time I deploy (with--keep-vars) I still get the prompt "You are about to publish a Workers Service that was last updated via the script API." and I have to say yes - then it works. But this breaks any automation/CI.
Is there a flag to always confirm the prompt? Or even better what is the recommend approach for this scenario?
Please ping me on response, thank you 🙂
0 Replies