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 a separate resource to manage ownership of UC objecs #4321

Open
alexott opened this issue Dec 14, 2024 · 0 comments
Open

[FEATURE] Add a separate resource to manage ownership of UC objecs #4321

alexott opened this issue Dec 14, 2024 · 0 comments
Labels
feature New feature or request

Comments

@alexott
Copy link
Contributor

alexott commented Dec 14, 2024

Databricks started to introduce UC objects that are created automatically, but for which we can change the owner. I.e., the __databricks_managed_storage_credential storage credential. We can't create it ourselves, but we still need to have an ability to change the ownership for it.

For such cases it would be nice to have a resource like databricks_uc_object_owner that could be used like this:

resource "databricks_uc_object_owner" "managed_storage_cred" {
  storage_credential_name = "__databricks_managed_storage_credential"
  owner = "<principal>"
}
@alexott alexott added the feature New feature or request label Dec 14, 2024
github-merge-queue bot pushed a commit that referenced this issue Dec 17, 2024
## Changes
<!-- Summary of your changes that are easy to understand -->

Databricks has started to introduce UC objects that are created and
managed by Databricks, i.e., storage credentials and external locations,
so we can't create resources to manage them.

This PR converts such managed UC objects into data sources so we can
attach permissions to them and handle references. The change of
ownership is still not implemented - filed
#4321
to handle it.

Other changes include:

- refactoring of creation of new resource data objects
- fixing a problem with the codegen of data sources, so we don't need a
dedicated `Body` implementation.

## Tests
<!-- 
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->

- [x] `make test` run locally
- [ ] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] using Go SDK
- [ ] using TF Plugin Framework
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

1 participant