[ISSUE] Issue with databricks_quality_monitor resource

[martin-walsh]

Configuration

data "databricks_table" "cleaned_events_table" {
  name = "my_catalog.my_schema.cleaned_events"
}

resource "databricks_sql_endpoint" "monitoring_serverless" {
  name = "my-serverless-warehouse-for-monitoring"

  cluster_size   = "2X-Small"
  auto_stop_mins = 1

  enable_serverless_compute = true
}

resource "databricks_quality_monitor" "cleaned_events_timeseries_monitor" {
  table_name         = data.databricks_table.cleaned_events_table.name
  assets_dir         = join(
    "/",
    [
      data.databricks_current_user.terraform_user.home,
      "some",
      "path",
      "to",
      "files",
    ]
  )
  warehouse_id       = databricks_sql_endpoint.monitoring_serverless.id
  output_schema_name =  "my_catalog.my_schema"
  time_series {
    granularities = ["1 day"]
    timestamp_col = "my_timestamp_col"
  }

  schedule {
    quartz_cron_expression = "0 0 4 * * ?"
    timezone_id = "UTC"
  }
}

Expected Behavior

Deploy should succeed.

Actual Behavior

Error when deploying quality monitor:

│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to databricks_quality_monitor.cleaned_events_timeseries_monitor, provider "provider[\"registry.terraform.io/databricks/databricks\"]"
│ produced an unexpected new value: .warehouse_id: was cty.StringVal("109a725fd8187d7e"), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Steps to Reproduce

1. terraform apply

Terraform and provider versions

- databricks/databricks v1.66.0

Is it a regression?

Unsure.

Debug Output

N/A. Environment is locked down.

Important Factoids

N/A.

Would you like to implement a fix?

Not sure where the problem lies, but happy to help if directed.