Exercise PostgreSQL ClickPipe creation through the live CLI

[sdairs]

Summary

• rename the required managed-Postgres CDC integration target and create its ClickPipe through the built clickhousectl binary
• verify the private-CA API failure and CLI guidance without --ca-certificate, then write the fetched CA bundle and verify successful creation, Running state, snapshot rows, and ongoing CDC
• build the CLI in the ClickPipes workflow and explicitly classify both the historical and renamed test paths
• document the renamed target, CLI build, and CLICKHOUSE_CLOUD_TEST_CLICKHOUSECTL_BIN requirement
• query CLI-created SharedMergeTree-backed tables without unsupported FINAL

Tests

• cargo test -p clickhouse-cloud-api --test clickpipe_postgres_cli_cdc_test
• cargo test -p clickhousectl --bin clickhousectl postgres_
• cargo test -p clickhousectl --test cli_request_shape_test postgres_
• python3 -m unittest discover -s scripts/tests -p "test_*.py"
• cargo fmt --all --check
• cargo clippy -p clickhouse-cloud-api -p clickhousectl --all-targets -- -D warnings
• Cloud Integration, clickpipes scope on 300a284d10856697058afdf041bd3ef5840d81d7

The credentialed live run passed. The managed Postgres fixture uses a private CA, so success without an uploaded CA remains a residual gap until CI provides a publicly trusted PostgreSQL source.

Closes #447

[sdairs]

Carry-over review from PR #503 (old PR for #447). Design-wise this PR is better than #503 (self-describing rename, extracted PostgresCliCreate arg builder with an offline unit test pinning the exact arg vector, defensive cleanup registration on unexpected success, error-before-hint ordering assertion, explicit --auth basic/--replication-mode cdc, corrected EC2-stage comment, no unexplained FINAL removal). Two required items that #503 already had:

1. No live Cloud CI execution exists for this PR. The entire point of issue Exercise PostgreSQL ClickPipe creation through the CLI in live CI #447 is live CLI coverage. Exercise PostgreSQL ClickPipe creation through the CLI in live CI #503 has a green credentialed Cloud Integration run (run 32751122188) and carries the run-cloud-integration label; this PR has neither, and its description admits the live test was not executed locally. Add the run-cloud-integration label and land a green Cloud Integration run on this branch before merging.

2. Documentation regression vs Exercise PostgreSQL ClickPipe creation through the CLI in live CI #503. Exercise PostgreSQL ClickPipe creation through the CLI in live CI #503 updated AGENTS.md and the clickhouse-cloud-api README; this PR touches neither, and after the test rename crates/clickhouse-cloud-api/README.md:~83 still documents the deleted clickpipe_postgres_cdc_test target and never mentions the required CLI build or the CLICKHOUSE_CLOUD_TEST_CLICKHOUSECTL_BIN env var; AGENTS.md's ClickPipes bullet does not mention the CLI dependency. Update both docs to the renamed target and the CLI-build requirement.

3. Minor (optional): inside the async test body, prefer the file's existing return Err(...) / TestResult convention over panicking assert!/assert_eq! for more actionable failure messages; and consider whether always passing --url (with a hardcoded production default) slightly reduces fidelity to the default CLI path.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e43ad29. Configure here.}

[cursor]

Relative CLI path fails locally

Low Severity

clickhousectl_binary checks CLICKHOUSE_CLOUD_TEST_CLICKHOUSECTL_BIN with is_file() against the test process working directory. Cargo sets that to the clickhouse-cloud-api package root, not the workspace. The documented target/debug/clickhousectl path is workspace-relative, so the live test rejects a valid binary. CI is unaffected because the workflow uses an absolute path.

Additional Locations (1)

• crates/clickhouse-cloud-api/README.md#L88-L94

 

^{Reviewed by Cursor Bugbot for commit e43ad29. Configure here.}