Open drewipsonhq opened 1 month ago
resource "databricks_model_serving" "this" { for_each = local.serving_endpoints provider = databricks.workspace name = each.key route_optimized = each.value.route_optimized config { served_entities { name = each.key entity_name = each.value.entity_name workload_size = each.value.workload_size scale_to_zero_enabled = can(each.value.scale_to_zero_enabled) ? each.value.scale_to_zero_enabled : true } traffic_config { routes { served_model_name = each.key traffic_percentage = 100 } } } dynamic "tags" { for_each = merge(local.static_tags, { for obj in local.dynamic_tags[each.key] : obj.key => obj.value }) content { key = tags.key value = tags.value } } }
My output (with nothing changed) shows the following plan:
# databricks_model_serving.this["stage-hq-ai-user-lookup"] will be updated in-place ~ resource "databricks_model_serving" "this" { id = "{id}" name = "{name}" # (2 unchanged attributes hidden) ~ config { ~ traffic_config { ~ routes { + served_model_name = "{same_value}" # (1 unchanged attribute hidden) } } # (1 unchanged block hidden) } # (4 unchanged blocks hidden) }
Nothing - the state matches so no update is required.
TF plan shows an update to the resource as it "does not match state".
Version 1.48.3
No. I tried 1.47.0
@drewipsonhq could you check if the fix in 1.49.0 resolves this?
Configuration
My output (with nothing changed) shows the following plan:
Expected Behavior
Nothing - the state matches so no update is required.
Actual Behavior
TF plan shows an update to the resource as it "does not match state".
Steps to Reproduce
Terraform and provider versions
Version 1.48.3
Is it a regression?
No. I tried 1.47.0