Per-Deployment Secrets?
I'm encountering an issue with Wrangler's secret management.
It seems that Wrangler doesn't support setting secrets on a per-deployment basis. This is causing problems because:
1. All branches that aren't 'main' are automatically treated as preview environments.
2. Changing the database configuration by environment means ALL preview environments are updated at once, even when intending to isolate a change to a single branch.
3. This means updating a configuration could break all branches on previous workers except the most recently deployed one.
Is there a way to set or override secrets on a per-deployment basis, rather than per-environment, that I'm not aware of? This is important to our desired development workflow.
Am I misunderstanding deployment vs environment in Workers terms?
Thanks for your help in clarifying this.
1 Reply
Hey there! Any updates to secret configuration take effect on the next deployment and will not impact prior deployments