Mohammad Naghavi
Mohammad Naghavi
I'm just calling wrangler with the option that sets configuration file directly to the generate file (something like `wrangler -c .output/server/wrangler.json ...`). generally my POV is that: 1. what wrangler...
wrangler itself creates different workers per env. Also I personally see a value in having all the config in a single file. but yes there are multiple solutions to this...
so after fighting with this for some time and in different projects, I also decided to just set the `deployConfig: false` and use the wrangler config for all stuff directly....
hitting the same problem would definitely go for for Option C if possible
@petebacondarwin as stated in the very first comment, it is about doing it atomically: code + secrets + env variables. the way it is now does not make an atomic...
I personally currently still use `wrangler.jsonc` for all env vars (secret or not) which is not a good practice but for this exact reason because now I can run a...