Operate an existing ClickHouse Cloud ClickPipe via the API: start, stop, resync, rescale, edit settings, and delete it

Documented steps

1. Authenticate with HTTP Basic auth (key ID as username, key secret as password) on every call.
2. Change lifecycle state: PATCH /v1/organizations/{organizationId}/services/{serviceId}/clickpipes/{clickPipeId}/state with {"command": ...}. The enum is exactly 'start', 'stop', 'resync' - there is no separate 'pause' command; use 'stop' to pause ingestion and 'start' to resume.
3. curl --user "$KEY_ID:$KEY_SECRET" -X PATCH -H 'Content-Type: application/json' https://api.clickhouse.cloud/v1/organizations/$ORG_ID/services/$SERVICE_ID/clickpipes/$PIPE_ID/state -d '{"command":"stop"}'
4. 'resync' applies to Postgres and MySQL pipes and swaps in freshly re-snapshotted tables. It is rejected for Kafka, Kinesis, object storage, BigQuery, and MongoDB pipes.
5. Rescale a streaming or object-storage pipe: PATCH .../clickpipes/{clickPipeId}/scaling with replicas, replicaCpuMillicores, and/or replicaMemoryGb. The older `concurrency` field is deprecated - prefer the CPU and memory fields.
6. Rescale database CDC pipes: GET /v1/organizations/{organizationId}/services/{serviceId}/clickpipesCdcScaling to read current values, then PATCH the same path with replicaCpuMillicores and replicaMemoryGb. This scales infrastructure shared by ALL database ClickPipes on the service, not one pipe, and only exists once a database pipe has been provisioned.
7. Tune advanced settings: PUT /v1/organizations/{organizationId}/services/{serviceId}/clickpipes/{clickPipeId}/settings with keys such as streaming_max_insert_wait_ms, object_storage_concurrency, object_storage_max_file_count, and clickhouse_max_threads. Because this is a PUT, read the current settings first and resend everything you want to keep.
8. Edit other fields (name, mutable source fields, destination, fieldMappings) with PATCH .../clickpipes/{clickPipeId}. For Kafka sources, brokers, topics, consumer group, format, offset, schema registry, and exactly-once semantics are effectively immutable after creation.
9. Delete with DELETE /v1/organizations/{organizationId}/services/{serviceId}/clickpipes/{clickPipeId}. This stops ingestion immediately and is irreversible.
10. After any state, scaling, or settings change, GET the pipe to confirm the change took effect - CDC scaling in particular can take several minutes to propagate.
11. Docs: https://clickhouse.com/docs/integrations/clickpipes and https://clickhouse.com/docs/integrations/clickpipes/postgres/pause_and_resume