databricks/terraform-provider-databricks v1.123.0

on GitHub

Important Changes

• Removed plan-time workspace_id reachability validation for unified-provider
  resources (#5887).

  workspace_id reachability and mismatch errors (e.g. workspace_id mismatch,
  managing workspace-level resources requires a workspace_id) are now reported
  when the resource is applied instead of during terraform plan. Plans no longer
  make workspace-resolution API calls for these checks. This fixes false-positive
  plan failures for principals that can manage a resource but cannot call the
  workspace /Me endpoint, and for provider_config.workspace_id values that are
  only known after apply (for example a workspace_id sourced from another
  resource that is created in the same run). For newly-created workspace-level
  resources this removes plan-time workspace API calls entirely; existing
  resources still refresh at plan (an unavoidable read), which validates the
  workspace they already live in.

New Features and Improvements

• Add databricks_recipients data source to list Delta Sharing recipient names.
• Add trace_location to databricks_mlflow_experiment for storing experiment traces in a Unity Catalog schema (#5869). The block is immutable (ForceNew); table_prefix is optional and, when omitted, server-defaulted, with the resolved value exposed on the read-only effective_table_prefix.

Bug Fixes

• Fix updating a column comment on a VIEW in databricks_sql_table (#5855). The provider emitted ALTER VIEW ... ALTER COLUMN ... COMMENT, which Databricks rejects with a PARSE_SYNTAX_ERROR, leaving the change stuck as a perpetual, un-appliable diff. Column comment changes on views are now applied in place via COMMENT ON COLUMN, matching how column comments on tables are updated.
• Fix databricks_access_control_rule_set drift detection when all grant_rules are removed outside Terraform (#5589).

Internal Changes

• A provider-level workspace_id is now consistently validated when a
  workspace-level resource acquires its client, regardless of whether the value
  came from the resource's provider_config block or the provider configuration
  (#5887).

  Previously a workspace-level provider silently ignored a mismatched
  provider-level workspace_id when a resource omitted provider_config. It now
  surfaces a workspace_id mismatch error at apply, matching the behavior when
  provider_config.workspace_id is set explicitly. For the common case where the
  provider-level workspace_id matches the configured workspace (including when
  it is auto-resolved from host metadata) there is no change.