It appears secrets can only be managed from the fly CLI as well as the UI. I would like the fly.toml file to be declarative in nature and so should be an all encompassing doc of the app. Currently, this misses any ability to record a required secret, one which must be set so that the machine can operate.
Will it be possible in future, or does Fly.io have a view on how this can be achieved?
Something like https://fly.io/docs/reference/configuration/#the-env-variables-section where you can define env variables on the fly toml file?
Yes, something like this is what I’m looking for. The values I need are sensitive though, so it would be preferred if I could define that the secret value is necessary, which Fly should then verify it has been set to something, but set manually and out of band, the deploy doesn’t need to set it.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.