docs(transformations): add external data sources guide - #2734
Draft
Khyat-Cognite wants to merge 1 commit into
Draft
docs(transformations): add external data sources guide#2734Khyat-Cognite wants to merge 1 commit into
Khyat-Cognite wants to merge 1 commit into
Conversation
Walks through registering a Fabric OneLake data source, checking that it is usable, reading its tables from transformation SQL with ext_onelake(), rotating the client secret and deleting the data source. The page is reached from the Transformations page and cross-references the API and data class reference there instead of repeating the autosummary and automodule directives.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Third and last PR in the stack: #2729 (data classes) → #2732 (client API) → this one. Review #2732 first; this diff is docs only.
Adds
docs/source/transformations_external_data_sources.rst, reached from a nested toctree on the Transformations page — the feature is one sub-API of transformations, not a family of its own, so it belongs under that page rather than as a peer entry inindex.rst.Contents
Concepts (format, credentials, location, data set scoping), a per-operation permission table, then task-oriented sections: register a data source, verify it is usable, read its tables from transformation SQL, list data sources, rotate the client secret, delete a data source.