databricks / terraform-provider-databricks

Databricks Terraform Provider
https://registry.terraform.io/providers/databricks/databricks/latest
Other
444 stars 382 forks source link

[ISSUE] Identity not found with `databricks_storage_credential` #3872

Open loonabunnie opened 1 month ago

loonabunnie commented 1 month ago

Configuration

provider "databricks" {
  host                        = local.databricks_workspace_host
  azure_workspace_resource_id = local.databricks_workspace_id
  azure_use_msi = true
}

resource "databricks_storage_credential" "ExternalCredentials" {

  name = "<Storage Credential Name>"
  azure_managed_identity {
    access_connector_id = "<Connector Id>"
    managed_identity_id = "<MSI Id>"
  }
  owner   = "<Storage Credential Owner>"
  comment = ""
}

Expected Behavior

Should be no gcp related parameters as I'm using azure managed identity

Actual Behavior

During Terraform plan, I am seeing this parameter

As stated in this docs, https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/storage_credential image databricks_gcp_service_account is for Databricks-managed GCP Service Account

Steps to Reproduce

Is it a regression?

--

Debug Output

2024-08-09T02:22:13.407Z [WARN] Provider "registry.terraform.io/databricks/databricks" produced an invalid plan for databricks_storage_credential.ExternalCredentials, but we are tolerating it because it is using the legacy plugin SDK. The following problems may be the cause of any confusing errors from downstream operations:

Important Factoids

--

Would you like to implement a fix?

--

nkvuong commented 1 month ago

does this results in an error, or is it just noise in the terraform plan? The databricks_storage_credential resource is cloud agnostic, so it would carry those attributes for other clouds, but it is not relevant in the case of aws or azure