Docs: sync upstream clickhouse-operator docs updates#47
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Syncs the four Kubernetes operator docs pages from
clickhouse/clickhouse-operator@b090fd8("docs: add Mintlify frontmatter to docs pages", #192) exactly as authored upstream.cc @Blargian for review (original author of the upstream changes).
Changes
products/kubernetes-operator/guides/configuration.mdx— synced from upstreamproducts/kubernetes-operator/guides/introduction.mdx— synced from upstreamproducts/kubernetes-operator/install/olm.mdx— synced from upstream (trailing newline)products/kubernetes-operator/reference/api-reference.mdx— synced from upstream (blank line after frontmatter)Frontmatter on these pages was already in place in this repo, so the only effective diffs are link-target paths and the small whitespace adjustments above.
mint broken-linksnow reports 6 broken links in the synced pages because the upstream uses unprefixed paths that don't exist in this Mintlify deployment (which serves the core docs under/core/...). These were previously rewritten in this repo and the upstream sync reverts them:products/kubernetes-operator/guides/configuration.mdx/concepts/features/configuration/server-config/configuration-files#example-1→ should be/core/concepts/.../reference/settings/server-settings/settings→ should be/core/reference/.../concepts/features/configuration/settings/settings-users→ should be/core/concepts/...products/kubernetes-operator/guides/introduction.mdx/reference/engines/database-engines/replicated(x2) → should be/core/reference/...Per the sync instructions these were copied as-is. They should be fixed upstream in
clickhouse/clickhouse-operator(either by adding the/core/prefix or by adjusting the sync workflow to rewrite paths) before merging this PR, otherwise the broken links will land in the deployed site.The pre-existing broken link in
integrations/language-clients/java/jdbc.mdxis unrelated to this sync.Context
Triggered by a merge to
main; the merged commit (e9a7419) was an unrelated experimental-settings sync. The actionable upstream change inclickhouse/clickhouse-operator/docsis commitb090fd8by @Blargian.