registry_config_path argument ignored?

[ntaylor-ads]

I am trying to use the provider inside of an Azure DevOps build agent. Unfortunately, the build agent lacks permissions to create the client registry at the default path. I attempted to choose a path the agent can write at by specifying registry_config_path, but the logs from the pipeline indicate that the argument is being ignored.

provider "helm" {
  kubernetes =  {
    host                   = azurerm_kubernetes_cluster.aks.kube_config.0.host
    client_certificate     = base64decode(azurerm_kubernetes_cluster.aks.kube_config.0.client_certificate)
    client_key             = base64decode(azurerm_kubernetes_cluster.aks.kube_config.0.client_key)
    cluster_ca_certificate = base64decode(azurerm_kubernetes_cluster.aks.kube_config.0.cluster_ca_certificate)
    config_path            = "~/.kube/config"
  }
  
  registry_config_path   = "/agent/_work/_temp/helm-registry-config.json"
  repository_config_path = "/agent/_work/_temp/helm-repositories.yaml"
  repository_cache       = "/agent/_work/_temp/helm-cache"
}

'''
╷
│ Error: Registry client initialization failed
│
│ with provider["registry.terraform.io/hashicorp/helm"],
│ on 1_providers.tf line 25, in provider "helm":
│ 25: provider "helm" {
│
│ Unable to create Helm registry client:
│ /home/adminuser/.config/helm/registry/config.json: stat
│ /home/adminuser/.config/helm/registry/config.json: permission denied
╵
'''

Terraform, Provider, Kubernetes and Helm Versions

Terraform version: 1.13.3
Provider version: 3.0.2
Kubernetes version:

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment