0

I have a self hosted agent. The service relies on DefaultAzureCredentials to use environment variables to connect to a Azure Key Vault. I rotated AZURE_CLIENT_SECRET and after remoting into the agent machine, I updated it as well. However after I ran a fresh build, the old value of that environment variable was used leading to connection failure. I have no specific cache task in the build pipeline.

Can someone help understand why an old value was used? Was it cached on the build agent or is it an issue with DefaultAzureCredentials implementation where credentials are cached?

shmit
  • 2,306
  • 2
  • 16
  • 20

0 Answers0