[ISSUE] Issue with `databricks_sql_permissions` resource

[nstans]

Configuration

File structure:

main.tf:

terraform {
  required_providers {
    databricks = {
      source  = "databricks/databricks"
      version = "~> 1.54.0" // for the succesful run ~> 1.38.0
    }
  }
}

provider "databricks" {
  host  = var.workspace_url
  token = var.pat_token
}

resource "databricks_sql_permissions" "sp_any_file" {
  any_file = true

  privilege_assignments {
    principal  = trimprefix("servicePrincipals/DONSENTMATTERPRINCIPAL", "servicePrincipals/")
    privileges = ["SELECT", "MODIFY"]
  }
}

variables.tf:

variable "pat_token" {
  type        = string
  description = "Export at runtime as ... export TF_VAR_pat_token=<Your PAT>"
  default     = ""
}

variable "workspace_url" {
  type        = string
  description = "Export at runtime as ... export TF_VAR_workspace_url=<Your workspace url> "
  default     = ""
}

Expected Behavior

Note: the service principal provided in the example is a trivial variable, the issue is that the compute does not initialise, which is the point of the minimum reproducible example.

Should fire up a compute on the workspace to lodge the SQL query like below. This successful execution was carried out with databricks provider 1.38

Actual Behavior

Error output to console and no compute initialised on workspace.

Error: cannot create sql permissions: Access mode LEGACY_SHARED_TABLE_ACL is not compatible with single-node mode. Only NO_ISOLATION and SINGLE_USER are supported.

Steps to Reproduce

1. Export your test workspace PAT token in console as per variable description
2. Export your workspace url like https://dbc-AAAAAAAA-1111.cloud.databricks.com in console as per variable description
3. Run terraform init from the root folder
4. Run terraform apply and confirm with yes

Terraform and provider versions

Terraform v1.9.5 on linux_amd64

• provider registry.terraform.io/databricks/databricks v1.54.0

Is it a regression?

This was working in terraform version 1.38, noticedthe issue when updating to 1.53, and still a bug on 1.54

Debug Output

Important Factoids

No

Would you like to implement a fix?

[alexott]

The problem here is more on the backend side - I can't create a cluster with such a configuration anymore. Most probably the 1.38 used the cluster created long time ago that was kept for compatibility reasons.

[NicholasFiorentini]

Maybe it is related to the permission refactoring done in 1.53? I also have a regression: https://github.com/databricks/terraform-provider-databricks/issues/4143.

[mgyucht]

For posterity, this is a separate issue from databricks_permissions.