Open allwritesri opened 1 year ago
Hi. Could you please take a look here: https://learn.microsoft.com/en-us/azure/developer/go/azure-sdk-authentication?tabs=bash#-option-2-use-a-managed-identity
It is probably needed to set AZURE_CLIENT_ID to the identity's client ID.
Is this still an issue?
Describe the bug I have followed the link provided in the documentation about the Azure KeyVault backend and that link suggests to follow Azure documentation which tells that for managed identity there isn't any need for credentials to be passed as long as the applications runs on an Azure Resource which is configured to use the managed identity.
I have setup the managed identity on the cluster which is running the AKS and also created one managed identity. However, there isn't any documentation provided to how to configure this for argocd-vault-plugin.
To Reproduce Steps to reproduce the behavior:
ARGOCD_ENV_AVP_TYPE
as azurekeyvault and setARGOCD_ENV_AZURE_TENANT_ID
as the tenantId of the azure subscription<path:secret-name>
could not unmarshal cluster secret {secret_name}
Expected behavior The secret should have got pulled from azure keyvault and replaced in the cluster.