GCP Cloud Run Instance Not Recognizing Environment Variable Changes in Deployed Services
I'm having a hard time understanding I've been banging my head against this for hours... I've been struggling with this for a few days now and could really use some help. I'm having trouble with my GCP Cloud Run service where it doesn't seem to pick up changes to environment variables after deploying a new revision. I updated an environment variable in the Cloud Run settings, but when I access the service, it still reflects the old value. I verified the deployment process, and there are no errors in the logs. Here's the command I used to deploy the Cloud Run service: ```bash gcloud run deploy my-service \ --image gcr.io/my-project/my-image:latest \ --update-env VAR_NAME=new_value \ --platform managed \ --region us-central1 ``` After deploying, I checked the value of the environment variable from within my Node.js application using: ```javascript console.log(process.env.VAR_NAME); ``` This still outputs the old value. I've also tried exploring the Cloud Run settings in the GCP console to confirm that the new environment variable value is set correctly. I am also using Node.js version 14.x and Express.js version 4.17.1. I expected that upon redeploying my service with the updated environment variable, it would reflect the new value immediately. I also attempted to delete the existing configuration and redeploy the service, but the old environment variable continues. Is there a caching mechanism I need to clear, or is there a specific step I might be missing? Any insights would be greatly appreciated! Has anyone else encountered this? I'm coming from a different tech stack and learning Javascript. I'm coming from a different tech stack and learning Javascript.