The logic behind a "Release" after adding a secret

[greg]

You’re welcome.

Kurt posted today they are close to fixing it

It’s because of how Fly’s innards work. The “3+ VMs” solution just masks it for now. There is some more detail from @kurt here on the cause:

how do fly.io deploys work?

You’re probably hitting a slow service propagation issue we’ve been fighting. It will hopefully be fixed for good in a few weeks, but the tldr is we’re probably causing the downtime when you deploy an app with a single VM. You can reduce the impact of this by running fly scale count 2 or more. When you deploy we: Start a canary VM (if you’re using a volume, we skip this step) Remove an old VM from service discovery Wait 30 seconds Stop old VM Start new VM, add it to service discovery fly-pro…