Issue with deployment picking old environment variables
Hi there is weird bug in one of my services. The deployment sometimes pick old environment config values. I had changed the config few weeks ago.
This happened to me just now. Is there anybody else facing this issue?
very scary because it picked the old database config that is not correct.
redeployed and it picked new config values
13 Replies
happened with me again
75a4791 this is the deployment id for debugging purposes
I redeployed -> 936fcb9
redeploy fixed the issue 😦
this is very scary folks. this makes the deployment unpredictable.
same issue once again
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
variable
>And are you using railway's databases?
yes, postgres
ac677073-a4cb-4ca1-a6d8-777b313fd4aa
plugin id ^
for your debuggingUnknown User•3y ago
Message Not Public
Sign In & Join Server To View
so the issue is that the deployment is picking old DATABASE_URL in every new commit deployment
if I redeploy, it picks the new one
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
you mean railway auto injects environment variables ?
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
sure
I should use a different environment variable then?
is that the recommendation ?
I have created my database on aws
initially it was on railway
I don't want to use that in my service
but I want to keep the database running on railway
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
cool. very weird bug
thanks
Confimred we are working on a fix for that bug!