Docs: sync upstream clickhouse-operator docs updates#39
Closed
mintlify[bot] wants to merge 1 commit into
Closed
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
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.
Summary
Syncs
products/kubernetes-operator/with the latestdocs/content fromClickHouse/clickhouse-operator(HEAD14b8f47), copied verbatim as instructed.cc @juliojimenez — original author of the upstream docs changes, please review.
Changes
Updated the following files from upstream
clickhouse-operator/docs/:products/kubernetes-operator/overview.mdxproducts/kubernetes-operator/guides/configuration.mdxproducts/kubernetes-operator/guides/introduction.mdxproducts/kubernetes-operator/install/helm.mdxproducts/kubernetes-operator/install/kubectl.mdxproducts/kubernetes-operator/install/olm.mdxproducts/kubernetes-operator/reference/api-reference.mdxConflicts / issues to fix upstream
Per instructions, files were copied exactly as they appear in
clickhouse-operator. This surfaces a few drift items between upstream and the Mintlify deployment that should be resolved upstream before this PR is merged:Missing Mintlify frontmatter. Upstream files no longer carry the Mintlify YAML frontmatter (
slug,title,keywords,description,doc_type,sidebarTitle,position). All seven files were affected. Without it, pages may render without correct titles/slugs/sidebar entries on the Mintlify site. Thereference/api-reference.mdxupstream still has partial frontmatter but is missingposition,doc_type, and uses a differentkeywordslist than the deployed copy.Broken internal links (confirmed by
mint broken-links). Upstream uses bare paths that don't exist on the Mintlify site, which prefixes them with/core/: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/...install/olm.mdxhas a stray trailing blank line upstream vs. the previous deployed copy. Cosmetic only.mint validatepasses;mint broken-linksreports the links above as broken (plus one unrelated pre-existing broken link inintegrations/language-clients/java/jdbc.mdxthat is out of scope for this sync).Context
Triggered by merge of
ClickHouse/mintlify-docs-dev#38(commita8d2652). Upstream HEAD synced from:ClickHouse/clickhouse-operator@14b8f47("feat(release): Create PR to community-operators after release (#190)").