[sdairs]

CLI exposure for the ClickPipes part of the #1112 drift remediation. Refs #1112. Stacked on CLI 1 (#1118, cursor/openapi-drift-1112-cli-postgres-c05d), which it merges; the syncCron library change it uses is in API 2 (#1119).

Follow-up issues

I can't open issues from this environment. This PR's tracking issue would read:

CLI: BigQuery ClickPipe sync schedules (#1112). Expose cloud clickpipe create bigquery --sync-cron. Not exposed: changing the schedule after creation, because the API has no BigQuery source update.

Changes

• clickpipe create bigquery --sync-cron <CRON> sends settings.syncCron. It takes a 5-field expression or a descriptor such as @hourly, in UTC unless prefixed with CRON_TZ=<zone>.
• It conflicts with --sync-interval-seconds, which clap reports as a usage error. Snapshot mode and blank values are rejected as usage errors before any request. The API validates the expression itself.
• docs/reference/clickpipe-configuration.md documents it in "Configure BigQuery CDC".

Tests

• Parsing (value preserved verbatim, conflict with --sync-interval-seconds).
• Request builder (exact settings JSON for an events-based CDC pipe).
• Validation (blank value, snapshot mode, both as usage errors).

Verification

cargo fmt --all --check, both clickhousectl clippy configurations, cargo check -p clickhousectl --no-default-features and cargo test -p clickhousectl all pass. No files added or renamed.

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}