feat(clickpipes): document clickpipes_egress_ips in static-ips API - #6596
Draft
whites11 wants to merge 1 commit into
Draft
feat(clickpipes): document clickpipes_egress_ips in static-ips API#6596whites11 wants to merge 1 commit into
whites11 wants to merge 1 commit into
Conversation
Adds the new per-region clickpipes_egress_ips field (from ClickHouse/data-plane-infrastructure) to the Cloud endpoints API reference, and a jq snippet on the ClickPipes 'List of Static IPs' page to fetch the NAT IPs programmatically. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
|
Thanks for contributing to the ClickHouse documentation! We’ve moved documentation development to the main ClickHouse/ClickHouse repository. For future documentation changes, please open your pull request there, with changes under the docs/ directory. We’ll continue reviewing this pull request here during the transition, and it will be transferred as part of the migration. You don’t need to reopen it. See the documentation README for more information. |
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
2 participants
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
Documents the new per-region
clickpipes_egress_ipsfield exposed byhttps://api.clickhouse.cloud/static-ips.json, which lists the static NAT IPs ClickPipes uses to egress to customer data sources.cloud/guides/data_sources/01_cloud-endpoints-api.md— notes the newclickpipes_egress_ipsfield in the schema description and adds it to the samplejq '.'output (using the real ap-south-1 ClickPipes NAT IPs).integrations/data-ingestion/clickpipes/index.md(#list-of-static-ips) — adds a tip withjqsnippets so customers can fetch the ClickPipes NAT IPs programmatically instead of copying the hand-maintained tables.Resolves the docs side of CLP-1115 — the customer asked for a
static-ips.json-style API for ClickPipes NAT IPs, mirroring the ClickHouse Cloud endpoints API.The
clickpipes_egress_ipsfield is added by data-plane-infrastructure PR #23468, which is currently dev-only. This docs PR must land only after the staging/prod rollout of that field, otherwise it documents a field that is not yet present in the productionstatic-ips.json. Keeping this as a draft until then.Notes
ru/zh/jpcopies are handled by the translation pipeline.🤖 Generated with Claude Code