Closed adriantorrie closed 3 years ago
@adriantorrie would you mind trying out the latest version v1.0.7 (released today) and see if that resolves your issue? I believe it should work as it was related to the task not setting some env vars that is used by the KeyVault secrets provider, as well as the login
command not using env vars defined in the executing process.
I believe on a self-hosted agent too the task extension should auto-update itself, but you can confirm the version being used by looking at the log for the Pulumi step. The version number of the task is printed at the beginning of the step.
@adriantorrie would you mind trying out the latest version v1.0.7 (released today) and see if that resolves your issue? I believe it should work as it was related to the task not setting some env vars that is used by the KeyVault secrets provider, as well as the
login
command not using env vars defined in the executing process.I believe on a self-hosted agent too the task extension should auto-update itself, but you can confirm the version being used by looking at the log for the Pulumi step. The version number of the task is printed at the beginning of the step.
Will give it a go sometime this week hopefully.
@adriantorrie I'll close this issue but please reopen or create a new issue if you have encountered other problems with using the latest version of the task extension in your self-hosted agent.
Describe the bug
pulumi up
fails on self-hosted agent, works perfectly on hosted agent.To Reproduce Steps to reproduce the behavior:
pulumi up
Expected behavior
pulumi up
works on self-hosted agentScreenshots None
Additional context
ubuntu:18.04
, the same error occursOn a self-hosted agent we have to assign the
kubeconfig
from Azure Key Vault, as the cluster is fire-walled and not accessible using Azure Devops Service Connections. Verification task is performed and works correctly.While the hosted agent uses a service connection for establishing the correct
kubeconfig