Skip to content

Conversation

@morsapaes
Copy link
Contributor

Adding a new integration guide for AlloyDB via the PostgreSQL ClickPipe.

@morsapaes morsapaes requested review from a team as code owners December 3, 2025 08:44
@vercel
Copy link

vercel bot commented Dec 3, 2025

@morsapaes is attempting to deploy a commit to the ClickHouse Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
Copy link

vercel bot commented Dec 3, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
clickhouse-docs Error Error Dec 3, 2025 8:58am
2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
clickhouse-docs-ru Ignored Ignored Preview Dec 3, 2025 8:58am
clickhouse-docs-zh Ignored Ignored Preview Dec 3, 2025 8:58am

</TabItem>
</Tabs>

## What's next? {#whats-next}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dhtclk @shawnclickhouse: could you point me to an example of how to create (and use) a template in Docusaurus? I want to add the steps to create a pipe to all service-specific guides, but am not super familiar with the framework.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@morsapaes you can create a markdown snippet (see here for examples).

You can then import them like this:

import CreateAPipe from '@site/docs/_snippets/_create_a_pipe.mdx.md';

<CreateAPipe/>

("CreateAPipe" can be any other arbitrary name)

The snippets themselves should not have any front-matter and should start with _ e.g. _create_a_pipe.mdx.
The snippets can go either in /docs/_snippets or alternatively in a _snippets folder alongside the ClickPipes docs.

import set_flags from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/alloydb/2_set_flags.png';
import verify_logical_replication from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/alloydb/3_verify_logical_replication.png';
import configure_network_security from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/alloydb/4_configure_network_security.png';
import configure_network_security2 from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/alloydb/5_configure_network_security.png';
Copy link
Member

@ilidemi ilidemi Dec 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The configure_network_security2 one doesn't seem to be referenced


3. Check the **Enable Public IP** checkbox to allow connections to the instance over the public internet. Under **Authorized external networks**, enter the [list of ClickPipes static IP addresses](../../../clickpipes/index.md#list-of-static-ips-list-of-static-ips) for the region your service is deployed in.

<Image img={configure_network_security} alt="Configure networking for public access with an IP allowlist" size="lg" border/>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(nit, up to you): Should the list of IPs on the screenshot be visibly truncated or have a label on top that both covers it and directs to use the list from the other page? Worry is that someone inattentive retypes it from the pic and gets surprised it doesn't work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants