Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Add account-level API support for UC resources #2179

Closed
nkvuong opened this issue Mar 31, 2023 · 5 comments
Closed

[FEATURE] Add account-level API support for UC resources #2179

nkvuong opened this issue Mar 31, 2023 · 5 comments
Labels
feature New feature or request

Comments

@nkvuong
Copy link
Contributor

nkvuong commented Mar 31, 2023

Account-level APIs are available for databricks_metastore, databricks_metastore_assignment and databricks_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 for databricks_metastore

Unity Catalog guides should also be updated to reflect this

@nkvuong nkvuong added the feature New feature or request label Mar 31, 2023
@john-auld
Copy link

john-auld commented May 16, 2023

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.

  1. databricks_metastore
  2. databricks_metastore_assignment
  3. databricks_catalog

There may be other problem with other resources that use the Workspace API, but creating two workspaces requires the following resource order.

  1. workspace a, using the mws provider.
  2. metastore, depends on workspace a
  3. unity catalog, depends on metastore
  4. workspace assignment, depends on metastore
  5. workspace b, depends on metastore and indirectly on workspace a.

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.

@alexandremoyrand
Copy link

hello @nkvuong

This issue along with the PR #2182 are very important for the deployment of our stack.
When do you think it will be released? is there any blocking point ?

Thanks

@vsluc
Copy link

vsluc commented Jun 11, 2023

Much important feature for our databricks adoption. Could we please prioritize this feature?

@peterutama
Copy link

I am in agreement, we are developing our deployment stack, and account level support for Unity catalog (#2182 and this PR) will be needed.

@mgyucht
Copy link
Contributor

mgyucht commented Aug 28, 2023

This is finally merged and released in the 1.24.0 release of the Terraform provider for Databricks.

@mgyucht mgyucht closed this as completed Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants