Environment Variables not found
I have existing serverless endpoints that were running without an issue. I run a check on start up to see if env vars exist, if not, I throw an error.
There was no issue with the endpoint previously but now it throws because of missing variables. I have checked the template, and the env vars still exist there.
Were any changes made in the last month that would cause this issue?
12 Replies
I am having the same issue!
The endpoint doesnt inherit the environtment variables from the template for some reason. Didnt happen to me before
I think setting the env vars in the Secrets section and them referencing them in the templates might work. I had them as strings in the template before. Replaced a few using the new secrets store and i got a new error for a different variable.
I'll know in about 15 minutes and update here if moving them all to secrets store works
I also contact RunPod via Email
Still not working. Tried to reference all env vars from secrets store, scaled workers to 0, then restarted endpoint with a new request. Same error exists
same issue
@flash-singh why would this happen?
is anyone referencing AWS keys specifically? That's my current issue. I know there is a way to set them in the handler input, I'm wondering if there is some kind of conflict
nope, but Firebase creds
@flavor-san Thanks, rules that out at least. And it seems like it's not just a me problem. That's both a relief and a concern
Solution
Hi, this has been fixed
Working for me after scaling workers to 0 and back up again