a month ago
TLDR
I added 2 new variables to a service and they were not injected after deployment. I think it's because I sealed the values before deploying the changes.
Full explanation
Added 2 different secrets as service variables to a backend app. After adding them, and before deploying the changes, I sealed the values. Then I deployed the changes but the service failed to start with logs showing both variables were missing.
I clicked "Edit" on one of the variables and filled the value again, after deployment logs showed it was now properly injected. Did the same with the other one and the service was able to start again.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The failed deployment's runtime logs show the app crashing repeatedly on a missing DATA_ENCRYPTION_ROOT_KEY variable, and the deployment that followed your re-edit of both values started and passed its healthcheck successfully. Your service is running normally now.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved sam-a • about 1 month ago