-
Notifications
You must be signed in to change notification settings - Fork 386
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 REQUEST] resource to manage UC tables/views owner #1267
Comments
Probably we'll just use owner field in the table resource |
Are you thinking to an upsert resource ?
|
though, on the other hand, if table schema evolution is controlled outside of terraform, the resource will constantly drift |
right, so a dedicated resource, or reusing the databricks_grants resource would be more appropriate |
databricks_grants uses different api, that is not managing ownership |
@ebarault currently it's easier for us to manage ownership in the resources themselves. |
Closed in #1338 |
hmm @nfx I believe it is not quite the same. What I was refering to is to change the ownership of already existing UC securables |
Thank you for the feature request! Currently, the team operates in a limited capacity, carefully prioritizing, and we cannot provide a timeline to implement this feature. Please make a Pull Request if you'd like to see this feature sooner, and we'll guide you through the journey. |
hi @nfx ! catching up here, is this still an ongoing issue ? or was it solve in the meantime ? |
Hi @nfx,
I'd like to suggest a new resource to manage UC tables/views owner, this could look like as simple as this:
Example configuration
It would also support the property
view
in addition totable
(mutually exclusive).Or maybe this could be merged with the
databricks_grants
resource, with an extraowner
property, but then it would imply managing the owner of any object managed by this resource : catalog/schema/table/viewRationale
The idea is that inside a company, one would often split the responsibilities regarding data schemas/permissions like this:
Along with managing permissions over these tables, managing owners of the tables/views also falls under dataops/devops responsibility. One trivial but systematic action is to switch owners from simple users to a groups.
Note: This module could also be thought generic enough to cover inclusion of other UC objects, such as UDFs.
Happy to discuss these rationales and implementation details
The text was updated successfully, but these errors were encountered: