You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
## 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
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:The text was updated successfully, but these errors were encountered: