➜ Projects fly secrets set -a app-name APP_SECRET='redacted'
Secrets are staged for the first deployment%
➜ Projects fly status -a app-name
Name = app-name
Owner = organisation
Hostname = app-name.fly.dev
Image = app-name:deployment-01GY7MKRNEQJ4882KASV6D4H1N
Platform = machines
ID PROCESS VERSION REGION STATE HEALTH CHECKS LAST UPDATED
3d8d9997f79578 web 2 fra started 2023-04-17T13:22:00Z
This should not be possible, right? I ran a deploy, set some secrets. Now I am trying to set some more secrets and it says “staged for first deployment”. What? I already have version 2 running
Machines apps stage secrets changes until you run a deploy. The deploy process updates secrets, we don’t implicitly start a deploy when you change them anymore.
Future versions of secrets will actually require a two step process: set them in our secrets storage, then update fly.toml to reference them as env vars. We can probably automate this when flyctl does it, but we’re still probably not going to trigger a deploy.