[Exporter] Correctly handle DB-managed UC objects #4323
+41
−26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
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:
Body
implementation.Tests
make test
run locallydocs/
folderinternal/acceptance