Closed nkvuong closed 1 year ago
Try creating two workspaces with Unity Catalog.
You will find that there are awkward resource ordering and dependency problems, which would not exist if the following resources used the Account API instead of the Workspace API.
There may be other problem with other resources that use the Workspace API, but creating two workspaces requires the following resource order.
In the Databricks E2 UI, the resources can be created manually, but the process is problematic in Terraform
Deleting workspace a would destroy the whole stack.
hello @nkvuong
This issue along with the PR https://github.com/databricks/terraform-provider-databricks/pull/2182 are very important for the deployment of our stack. When do you think it will be released? is there any blocking point ?
Thanks
Much important feature for our databricks adoption. Could we please prioritize this feature?
I am in agreement, we are developing our deployment stack, and account level support for Unity catalog (#2182 and this PR) will be needed.
This is finally merged and released in the 1.24.0 release of the Terraform provider for Databricks.
Account-level APIs are available for
databricks_metastore
,databricks_metastore_assignment
anddatabricks_storage_credential
.Need to add support to use these resources with provider that are defined against account-level url
No parameters change required, except for an additional
region
parameter fordatabricks_metastore
Unity Catalog guides should also be updated to reflect this