-
Notifications
You must be signed in to change notification settings - Fork 477
Open
Labels
TriagedThe issue has been reviewed. Issues without a “Triaged” label require triage/review.The issue has been reviewed. Issues without a “Triaged” label require triage/review.
Description
When running the terraform plan the following was the changes to be updated
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# databricks_catalog.glue_uc_catalog will be updated in-place
~ resource "databricks_catalog" "glue_uc_catalog" {
id = "glue-dev"
name = "glue-dev"
~ options = {
~ "authorized_paths" = "s3://glue-dev-logs/" -> "s3://glue-dev-logs/,s3://glue-dev-additional-logs/"
}
# (7 unchanged attributes hidden)
}but the terraform apply failed with the following error
Error: cannot update catalog: Modifying predictive optimization is unsupported for this catalog.Important note
glue-dev is a FOREIGN_CATALOG. Due to that, the concept predictive optimization does not make any sense because the actual catalogue is is not managed by databricks and hence cannot do any predictive optimization. This feels like a leaky API abstraction to the databricks_catalog resource, probably foreign catalogues should have a separate API and resource.
Terraform and provider versions
Terraform version: 1.9.8
Provider version: 1.80.0Metadata
Metadata
Assignees
Labels
TriagedThe issue has been reviewed. Issues without a “Triaged” label require triage/review.The issue has been reviewed. Issues without a “Triaged” label require triage/review.