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
#Issue with deployment picking old environment variables
valid flicker
valid flicker
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.
valid flicker
same issue once again
rigid birch
In which format do you store your database config? (file/variable/etc?)
And are you using railway's databases?
valid flicker
variable
And are you using railway's databases?
yes, postgres
ac677073-a4cb-4ca1-a6d8-777b313fd4aa
plugin id ^
for your debugging
rigid birch
Can I get a screenshot of variable's page?
valid flicker
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
rigid birch
Ah, Please delete DATABASE_URL.
Railway auto injects code if your database is there in the same project.
valid flicker
you mean railway auto injects environment variables ?
rigid birch
Yes, database's environment variables.
valid flicker
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
rigid birch
Ah, then you'll have to rename it to something else.