Open MohnJadden opened 1 year ago
I am facing the same issue.
By looking at the source code where the error comes from, it looks like the provider is failing to detect the HTTP client configuration for Azure.
https://github.com/databricks/terraform-provider-databricks/blob/b52eed9de62e43a17895e99406ee3bed699a7e72/secrets/resource_secret_scope.go#L68 https://github.com/databricks/terraform-provider-databricks/blob/b52eed9de62e43a17895e99406ee3bed699a7e72/common/client.go#L148
I couldn't find any relevant information in the debug log so far.
You are missing host
property or azure_workspace_resource_id
: https://registry.terraform.io/providers/databricks/databricks/latest/docs#azure_workspace_resource_id
@alexott I had that commented out in the original above. The provider block doesn't allow the use of each.key, so it can't read the resource ID of the Databricks resource we're trying to create.
This presents a bit of an issue. This module is meant to create Azure Databricks workspaces. The workspace URL is not available until it's created. How are we meant to define a host for the provider to use since it's a brand new resource and it won't allow the use of a loop? This would mean we'd have to create static main.tf files and define each individual environment, which is not really how we want to proceed.
Configuration
Expected Behavior
The Key Vault should be created and allow my user account to create/delete/get/list/set secrets. A secret scope should be created within the Databricks workspace. The secret scope should be able to talk to the Key Vault specified in each key.
Actual Behavior
The Key Vault is created, but we receive an error:
The error recurs whenever we run
terraform apply
after the initial creation.Steps to Reproduce
terraform apply
yes
to apply changesTerraform and provider versions
Debug Output
(https://gist.github.com/MohnJadden/f945f60bd1b50fcb7bdb18096b18eed7)
Important Factoids
The error recurs even if I delete the entire resource group that Terraform creates and I re-create it. I noticed in the debug logs that it was erroring out that I don't have access to certificate ManageContact perms on the Key Vault, but even if I add that permission to my access policy on the KVs, the error continues.