secret propagation unclear with `fly secrets set`

Questions / Help Build debugging
, ,
1

Hi there. We’ve been using fly.io very successfully over the past year to manage our deployments and staging servers. But today were unable to update the secrets on our machine from the flyctl cli. This is after adding a postgres managed instance to our vps and attempting to add the postgres database url as a secret.

for some reason no matter what we do (bringing down machines and creating new ones), we are unable to get the new secrets we added to propagate. we have tried to deploy the secrets, remove the machines, restart the app, to no avail. All i can find in the help topics is others have had similar issues with adding secrets to the UI. however its not clear if the secrets will propagate later or if they are just stuck at an older version which we can not control.

Any help debugging the matter would be appreciated. As we really need to get this instance deployed.

2

upon further investigation we have narrrowed down that the issue may be related to the build time behavior of deployments. right now our builds are failing, as a result of the secrets we are looking for not being present.

is it the case that secerts are not injected pre build time? if so, this basically means that we can only rely on loading secrets after the image is built and pushed to a machine. This is a reasonable workaround, but not clear to us if this is expected behavior :slight_smile: any advise here would be greatly appreciated.

3

this is correct. Build Secrets · Fly Docs

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.