Skip to content

Make PostgreSQL ClickPipe TLS failures actionable - #494

Open
sdairs wants to merge 2 commits into
issue-449-postgres-clickpipe-validationfrom
issue-446-clickpipe-tls-guidance-v2
Open

Make PostgreSQL ClickPipe TLS failures actionable#494
sdairs wants to merge 2 commits into
issue-449-postgres-clickpipe-validationfrom
issue-446-clickpipe-tls-guidance-v2

Conversation

@sdairs

@sdairs sdairs commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • document secure PostgreSQL ClickPipe TLS defaults and the conditional --ca-certificate / --tls-host behavior in command help
  • add public-trust and private-CA README examples plus networking, logical replication, publication, and privilege prerequisites
  • preserve original API errors while adding narrowly matched guidance for x509 unknown-authority and hostname-mismatch failures
  • keep PostgreSQL TLS bypass flags unavailable

Verification

  • cargo test -p clickhousectl cloud::clickpipes::tests (44 passed)
  • cargo test -p clickhousectl --test cli_request_shape_test postgres_ (26 passed)
  • cargo fmt --all --check
  • cargo clippy -p clickhousectl --all-targets -- -D warnings
  • cargo test -p clickhousectl (748 passed)
  • all three added ClickHouse documentation links returned HTTP 200
  • live Cloud/PostgreSQL ClickPipe creation not run because this environment has no dedicated source or Cloud integration credentials

Stack

Position: 2 of 2. Based on #484 (issue-449-postgres-clickpipe-validation); that parent remains unchanged.

Closes #446

@sdairs sdairs changed the title issue 446 clickpipe tls guidance v2 Make PostgreSQL ClickPipe TLS failures actionable Aug 24, 2026
Comment thread README.md

- Make the source reachable from ClickPipes and allow the [ClickPipes static IPs](https://clickhouse.com/docs/integrations/clickpipes/networking/static-ips) for your service region.
- Enable logical replication on PostgreSQL.
- Create a publication that includes every source table passed with `--table-mapping`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟠 High README.md:816

The PostgreSQL examples omit --publication-name, so following these instructions can make pipe creation enter the API's auto-create path and fail for users who only granted the documented schema, table, and replication privileges (or use a different publication). Add --publication-name <created-name> to both examples, or document the additional CREATE/ownership permissions required for auto-creation.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file @README.md around line 816:

The PostgreSQL examples omit `--publication-name`, so following these instructions can make pipe creation enter the API's auto-create path and fail for users who only granted the documented schema, table, and replication privileges (or use a different publication). Add `--publication-name <created-name>` to both examples, or document the additional `CREATE`/ownership permissions required for auto-creation.

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.

Make PostgreSQL ClickPipe TLS failures actionable

1 participant