Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
72 changes: 56 additions & 16 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 2 additions & 4 deletions crates/clickhouse-cloud-api/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,8 @@ uuid = { version = "1", features = ["serde", "v4"] }
chrono = { version = "0.4", features = ["serde"] }

[dev-dependencies]
# No `credentials-login`: through aws-config 1.13.0 it pulls p256 0.13 and
# crypto-bigint 0.5.5 (RUSTSEC-2026-0387). Restore it once aws-config ships
# smithy-lang/smithy-rs#4970 (p256 0.14).
aws-config = "1.8.16"
# `credentials-login` lets the default credential chain read `aws login` sessions.
aws-config = { version = "1.13.2", features = ["credentials-login"] }
aws-credential-types = "1.2.14"
clickhouse-openapi-analyzer = { path = "../clickhouse-openapi-analyzer" }
# Disable default features on aws-sdk-* crates to drop the legacy `rustls` feature,
Expand Down
2 changes: 1 addition & 1 deletion docs/development.md
Original file line number Diff line number Diff line change
Expand Up @@ -190,7 +190,7 @@ cargo test --test clickpipe_postgres_ec2_test -- --ignored --nocapture # per-s
cargo test --test clickpipe_smoke_test -- --ignored --nocapture # create-only smoke against a shared service
```

The suites load AWS credentials through the default provider chain: environment variables, shared profiles, SSO, or `credential_process`. `aws login` sessions are not read directly. To use one, export its credentials first with `eval "$(aws configure export-credentials --format env)"`.
The suites load AWS credentials through the default provider chain: environment variables, shared profiles, SSO, `aws login` sessions, or `credential_process`.

All require `CLICKHOUSE_CLOUD_API_KEY`, `CLICKHOUSE_CLOUD_API_SECRET`, `CLICKHOUSE_CLOUD_TEST_ORG_ID`, `CLICKHOUSE_CLOUD_TEST_PROVIDER`, and `CLICKHOUSE_CLOUD_TEST_REGION` in the environment, and are wired into the scheduled `Cloud Integration` GitHub Actions workflow. The ClickPipes E2E suites additionally need AWS credentials and an `eu-west-1` region quota; `clickpipe_smoke_test` reads a pre-provisioned service ID from `CLICKHOUSE_CLOUD_TEST_CLICKPIPE_SERVICE_ID`. The Postgres suite's private endpoint phase runs only on AWS with `CLICKHOUSE_CLOUD_POSTGRES_PRIVATE_ENDPOINT` set, because private endpoints need an organization with the feature enabled; creation adds 5 to 10 minutes.

Expand Down
Loading