Service hangs if env vars have bad secret

Troubleshooting and help
1

If you service has an env var pointing to a @sercret, but that @secret doesn’t exist, the instance will hang on re-deployment, forever, with no explanation that something is wrong.

For example, if a service has

MY_VAR=@MY_SECRET_VAR

Now, delete MY_SECRET_VAR from the secrets area. Now re-deploy the instance and see that it hangs. No log messages…no warning that @secret went away.

2

Hi Scott,

Indeed this is an issue. We have a feature request publicly open to vote.

When we prioritize it, the idea is to prevent deleting secrets used in a Service. It will prevent the scenario you have described to happen.

I’ll add your vote to it on your behalf.