DATABASE_URL not found in fly during deployment
Bug??
wasp deploy fly deploy fails with DATABASE_URL error even though secret exists (v0.15.2)
I'm getting a deployment blocker where wasp deploy fly deploy fails with:
Your server app does not have a DATABASE_URL secret set. Perhaps you need to create or attach your
database?
The issue: DATABASE_URL IS set and the app is running fine in production. The bug is that Wasp runs flyctl
secrets list -j, receives DATABASE_URL in the response, but still reports it missing.
Evidence:
# DATABASE_URL exists in Fly secrets
$ wasp deploy fly cmd secrets list --context server | grep DATABASE_URL
DATABASE_URL 44432e8ef938bde0
# But wasp deploy fails, even though it gets DATABASE_URL back
$ wasp deploy fly deploy
[... builds successfully ...]
$ flyctl secrets list -j
[{"name": "DATABASE_URL", "digest": "44432e8ef938bde0"}, ...]
Your server app does not have a DATABASE_URL secret set.
Deploy command failed with exit code: 1
wasp deploy fly deploy fails with DATABASE_URL error even though secret exists (v0.15.2)
I'm getting a deployment blocker where wasp deploy fly deploy fails with:
Your server app does not have a DATABASE_URL secret set. Perhaps you need to create or attach your database?
The issue: DATABASE_URL IS set and the app is running fine in production. The bug is that Wasp runs flyctl
secrets list -j, receives DATABASE_URL in the response, but still reports it missing.
Evidence:
# DATABASE_URL exists in Fly secrets
$ wasp deploy fly cmd secrets list --context server | grep DATABASE_URL
DATABASE_URL 44432e8ef938bde0
# But wasp deploy fails, even though it gets DATABASE_URL back
$ wasp deploy fly deploy
[... builds successfully ...]
$ flyctl secrets list -j
[{"name": "DATABASE_URL", "digest": "44432e8ef938bde0"}, ...]
Your server app does not have a DATABASE_URL secret set. Deploy command failed with exit code: 1
