Coding HAMA

While upgrading terraform azurerm provider from v2.6.4 to v2.81.0, terraform apply   complained about the managed virtual network on Azure Data Factory. Error: updating Data Factory: (Factory Name "adf-xxxx" / Resource Group "rg-xxxx"): once Managed Virtual Network has been Enabled it's not possible to disable it │ │ with module.data_factory.azurerm_data_factory.data_factory_xxx, │ on modules/data_factory/main.tf line 9, in resource "azurerm_data_factory" "data_factory_xxx": │ 9: resource "azurerm_data_factory" "data_factory_xxx" { This happened because azurerm v2.81.0 is restaging the resource (data factory) with a new schema, and while doing so, the managed virtual network enabled outside of the terraform became an issue. According to the error log, the terraform seems to disable the existing managed virtual network, while I want to leave it enabled.  Fortunately, there was a managed_virtual_network_enabled para...

Problem While trying to upgrade terraform provider azurerm from v2.6.4 to v3.10.0, I faced the following error when I ran terraform plan.  cannot configure azure-client-secret auth: cannot get workspace: please set `azure_workspace_resource_id` provider argument. Attributes used: auth_type. Environment variables used: ARM_CLIENT_SECRET, ARM_CLIENT_ID, ARM_TENANT_ID. Please check https://registry.terraform.io/providers/databrickslabs/databricks/latest/docs#authentication for details Databricks authentication, which used to work fine, suddenly stopped working with the version change, saying that azure_workspace_resource_id is not set while it is there. provider "databricks" {     azure_workspace_resource_id = < databricks_workspace_id> } The terraform version I used was v1.2.3, and the databricks provider was v1.0.0. The authentication failed not only for azure-client-secret but also with azure-cli. Try 1 (x) provider "databricks" {     a...