WARN KEY may be a potentially sensitive environment variable. Consider setting it as a secret, and removing it from the [env] section: https://fly.io/docs/reference/secrets/
KEY
WARN KEY may be a potentially sensitive environment variable. Consider setting it as a secret, and removing it from the [env] section: https://fly.io/docs/reference/secrets/
KEY
WARN KEY may be a potentially sensitive environment variable. Consider setting it as a secret, and removing it from the [env] section: https://fly.io/docs/reference/secrets/
KEY
WARN PRIVATE may be a potentially sensitive environment variable. Consider setting it as a secret, and removing it from the [env] section: https://fly.io/docs/reference/secrets/
PRIVATE
This is a weird warning for a couple reasons:
- I don’t have a variable named
KEY
orPRIVATE
. I have one namedAC_APP_KEY
and one namedPRIVATE_IMAGE_BUCKET
. - Neither of those variables is secret.
Is there a way to silence the warning for these variables that I know are safe?
Is there a way to fail my deploy instead of showing a warning if a new potentially sensitive variable is added?
The warning as it stands is noisy FUD, but if it’s given some bite (and actually fails the deploy) and I can explicitly override it when I know it’s safe, then I guess it could be a helpful point of reflection to leave it in. Otherwise, I’d like to just blanketly disable it.