[DOCS-15447] De-duplicate remaining BI integration docs - #39739
Draft
evazorro wants to merge 1 commit into
Draft
Conversation
Contributor
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.
What does this PR do? What is the motivation?
Fixes DOCS-15447
This is the follow-up to the Hex proof of concept, applied to the remaining five BI integrations: Looker, Tableau, Sigma, Power BI, and Metabase.
Each of these integrations has two copies of its docs — one under
integrations/generated from the integration README, and one underdata_observability/. The two have drifted. This PR keeps theintegrations/version as the single source of truth and reduces eachdata_observability/page to a stub: what the integration is for, the data warehouse prerequisite, and a link to the integration docs for setup.data_observability/paths, and the pages still exist, so nothing breaksMerge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Claude Code to diff each pair of docs, identify what content existed only in the Data Observability copy, and draft the stubs. Information architecture decisions, the Metabase scoping call, and this description by me.
Additional notes
Companion PRs move the content that only existed in the Data Observability copies into the integration READMEs:
Note that
hugo/data/partials/platforms.yamlhas an unrelated local change in my working tree that is deliberately not included here.