Hi
After updating from Databricks TF Provider from 1.49.1 to 1.50 we receive the error "ERROR: Tenant shouldn't be specified for managed identity account".
The configuration of the provider didn't change.
We have a TF module that creates a Workspace. After that, the provider is initialized with the URL of the created workspace.
module "dbx" {
...
}
provider "databricks" {
alias = "main"
host = module.dbx.ws_url
}
After that, we pass that provider to another module which then takes care of the "detail configuration" of the workspace.
#################################################################
# finally test this module
#################################################################
module "dbxconfig" {
providers = {
databricks = databricks.main
azurerm = azurerm
}
source = "../module"
depends_on = [module.dbx.ws_url]
whitelist_azure_service_tags = ["PowerBI"]
ip_restrictions = ["1.1.1.1"]
}
After updating to 1.50, we received the following error, after "apply" (plan did work):
│ Error: cannot create workspace conf: failed during request visitor: default auth: azure-cli: cannot get access token: ERROR: Tenant shouldn't be specified for managed identity account
│ . Config: host=https://adb-2665674642156245.5.azuredatabricks.net/, azure_use_msi=true, azure_tenant_id=af7227b1-ac3a-4487-9e9f-ba462bb409d4. Env: ARM_USE_MSI, ARM_TENANT_ID
│
│ with module.dbxconfig.databricks_workspace_conf.workspace_conf,
│ on ../module/main.tf line 4, in resource "databricks_workspace_conf" "workspace_conf":
│ 4: resource "databricks_workspace_conf" "workspace_conf" {
There were NO other changes other than updating the Terraform Provider. (We have an automated renovate process that ensures this was the only change in the merge request.)
NOTE: This happens on the automated build system, which of course has several environment variables concerning Azure set, like ARM_USE_MSI, ARM_TENANT_ID.
Expected Behavior
It should work as it did with 1.49.1
Actual Behavior
Provider initialization fails.
│ Error: cannot create workspace conf: failed during request visitor: default auth: azure-cli: cannot get access token: ERROR: Tenant shouldn't be specified for managed identity account
│ . Config: host=https://adb-2665674642156245.5.azuredatabricks.net/, azure_use_msi=true, azure_tenant_id=af7227b1-ac3a-4487-9e9f-ba462bb409d4. Env: ARM_USE_MSI, ARM_TENANT_ID
│
│ with module.dbxconfig.databricks_workspace_conf.workspace_conf,
│ on ../module/main.tf line 4, in resource "databricks_workspace_conf" "workspace_conf":
│ 4: resource "databricks_workspace_conf" "workspace_conf" {
Steps to Reproduce
Change Provider version from 1.49.1 to 1.50
Terraform and provider versions
Databricks Terraform Provider version 1.50
Is it a regression?
Other merge requests/branches, that use 1.49.1 are still working.
Hi
After updating from Databricks TF Provider from 1.49.1 to 1.50 we receive the error "ERROR: Tenant shouldn't be specified for managed identity account".
The configuration of the provider didn't change.
We have a TF module that creates a Workspace. After that, the provider is initialized with the URL of the created workspace.
After that, we pass that provider to another module which then takes care of the "detail configuration" of the workspace.
After updating to 1.50, we received the following error, after "apply" (plan did work):
There were NO other changes other than updating the Terraform Provider. (We have an automated renovate process that ensures this was the only change in the merge request.)
NOTE: This happens on the automated build system, which of course has several environment variables concerning Azure set, like ARM_USE_MSI, ARM_TENANT_ID.
Expected Behavior
It should work as it did with 1.49.1
Actual Behavior
Provider initialization fails.
Steps to Reproduce
Change Provider version from 1.49.1 to 1.50
Terraform and provider versions
Databricks Terraform Provider version 1.50
Is it a regression?
Other merge requests/branches, that use 1.49.1 are still working.