[ISSUE] Issue with `databricks_sql_alert` resource

[junwei-db]

We've only seen this happening in staging regions so far.

Configuration

# Copy-paste your Terraform configuration here
# databricks_sql_alert.table_freshness_foresight_routing_dlt_table_lineage_materialized_alert will be updated in-place
  ~ resource "databricks_sql_alert" "table_freshness_foresight_routing_dlt_table_lineage_materialized_alert" {
        created_at = "2023-09-20T21:08:11Z"
        id         = "449ea3d0-30c5-4fed-93fe-7517015bbd4a"
        name       = "[SEV2] Table Freshness: foresight.routing_dlt.table_lineage_materialized (staging-aws-us-west-2)"
        parent     = "folders/2635564422777671"
        query_id   = "9488110a-9f1e-4da2-8b50-6a452ce6198f"
        rearm      = 86400
        updated_at = "2024-04-25T03:57:37Z"

      ~ options {
            column         = "diff_minutes"
            custom_subject = "Alert {{ALERT_NAME}} changed status to {{ALERT_STATUS}}"
            muted          = false
            op             = ">"
          ~ value          = "120" -> "180"
        }
    }

Expected Behavior

Alerting threshold increased from 120 to 180 after deployment.

Actual Behavior

Alerting threshold remains unchanged after deployment.

Steps to Reproduce

1. Change some property of databricks_sql_alert
2. Deploy to staging regions

Terraform and provider versions

1.30.0

Is it a regression?

Yes.

Debug Output

Important Factoids

Would you like to implement a fix?

[alexott]

If it happens in specific regions only, and there is no changes in TF version, then it's backend problem, not a Terraform problem.