Donatas Mažionis

Same issue with AWS, provider version `1.34.0`. Minimal repro: ```hcl variable "unity_catalogs" { type = set(string) default = ["staging"] } # Account level catalog owners resource "databricks_service_principal" "catalog" { for_each...

Setting `metastore_id` fixes `ENDPOINT_NOT_FOUND` error: ```hcl resource "databricks_storage_credential" "catalog_staging" { name = "catalog_staging" owner = databricks_service_principal.catalog["staging"].application_id metastore_id = databricks_metastore.unity_metastore.id aws_iam_role { role_arn = "arn:aws:iam::1234567890:role/MyRole-AJJHDSKSDF" } provider = databricks.account } ```...

https://github.com/databricks/terraform-provider-databricks/pull/3184 fixes the issue

Issue can be reproduced on AWS as well. As a workaround, running `apply` again helps and `databricks_catalog` is created.