v0.6.0 plan: open issues, priorities and API-team blockers

Open
  • Is something wrong?
#1,182 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
5/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
aws, postgresql, rust
Domain
cli, cloud, databases, devtools

Research direction

This is a release-planning tracker, not a single task, so start with the untracked cargo audit failure in audit.yml: RUSTSEC-2026-0387 comes through aws-config to p256 and crypto-bigint 0.5.5. Each linked item is a separate issue or pull request with its own owner, and the stack is meant to merge together. Done means the listed issues and PRs are closed or moved to a follow-up, which a newcomer should not take on alone.

Written by the indexing model from the issue text.

Description

Replaces #939 (v0.5.1 follow-ups) and #757 (v0.5.0, shipped 2026-10-22). Based on a triage of all open issues on 2026-11-02.

Untracked: cargo audit is failing on main

audit.yml has failed on main every day since 2026-10-29: RUSTSEC-2026-0387 in crypto-bigint 0.5.5, reached through aws-config → p256 (credentials-login feature), a dev-dependency of clickhouse-cloud-api. Shipped binaries are not affected, but it turns every PR red (#1178, #1179). Fix by trimming aws-config features or bumping it.

Stack #1153: review and merge

These close when the stack merges:

  • #1144 OpenAPI drift (18 gaps), with #1147 (MongoDB mongoConfig) and #1148 (ClickStack log source expressions)
  • #1142 resolve the latest version from builds.clickhouse.com (PR #1143)
  • #1156 route Cloud Postgres handlers through CloudClient wrappers (PR #1165)
  • #1157 split oversized Cloud modules (services, postgres, organizations in this stack; clickpipes and clickstack still to do)
  • #1077 read-only local commands create project state (PR #1166)
  • #1159 rename local server to local clickhouse, add postgres list and local status (PR #1169)
  • #1158 pin subcommand order in --help (PR #1171)
  • #1164 write Cloud service connection settings to .env (PR #1167)
  • #1173 finish the clickhouse-cloud-api module split (PRs #1176–#1181)

Note: #1149 fails spec_coverage_test on its own head (the ClickStack fields arrive in #1151), so merge the stack together rather than one PR at a time.

Ready to work, in priority order

  1. #1160 local Postgres container names collide across projects (hits parallel worktree agents)
  2. #1072 carry the other program's error text in a details field of local JSON errors instead of redacting it
  3. #1065 unify the Cloud service poll loops
  4. #129 install or link locally built ClickHouse binaries
  5. #1162 next-step polling hints in JSON for asynchronous Cloud operations
  6. #1163 one status command for CLI, auth, project and skills context (settle naming against local status from #1159 first)
  7. #1161 command search for agents
  8. #1131 Cloud access request flow (PR #1132 needs review)
  9. #1062 always-applied config.d (settle the open questions first)
  10. #1064 local server selection (query telemetry first, then choose A or B)
  11. #1096 local Postgres on the pg_clickhouse image (draft PR #1097; weigh against the native bundle prototype in PR #1098)
  12. #1154 direct Cloud database connections with JWT (phase 1 can start now; phases 2–3 wait on the Cloud team)
  13. #800 connection profiles and MCP export (POC in PR #1061)
  14. #915 override for agent-detected JSON output (run the eval; shares a harness with #1161)
  15. #1155 shell completions
  16. #250 opt-in global data directories (revisit after #1062)
Unblocked from the API-team list (2026-11-02)

Answered by reading the control-plane and backend source. Each issue has a findings comment and, where something needs changing upstream, a link to a control-plane issue. These are small help, docs and validation changes.

  1. #841 require Kafka authentication locally (exit 2), matching the API
  2. #845 validate that fieldMappings exactly match destination.columns, for every source kind
  3. #824 reject settings in a whole-pipe update file and point to clickpipe settings update
  4. #926 state-command help from the real guard table; say that start on a Completed pipe has no effect
  5. #835 rewrite switchover help: it replaces the primary with a fresh server, works without HA, and may wait for the maintenance window
  6. #797 say that slowquery get --timestamp is ignored by the API, and correct the list window to inclusive
  7. #931 upper-case --severity, list the values, and warn on unknown ones
  8. #935 document replica and restore passwords (docs only)
  9. #937 document null, omit and reset semantics for settings (docs only)

In progress elsewhere

  • #1174 cut local test run time
  • #1175 remove low-value local tests, one-layer-per-behaviour rule

In scope for v0.6.0, blocked on the API team

Upstream issues raised on 2026-11-02, after reading the control-plane and backend source. The CLI-side steps for #797, #824, #835, #841, #926 and #931 are in the ready list above; what remains here is the upstream part.

  • #796 slow-query duration types: spec-only fix in ClickHouse/control-plane#40265 (assigned). No CLI work; close once the spec is corrected.
  • #797 timestamp grammar, and the detail timestamp the backend ignores: ClickHouse/control-plane#40266 (assigned).
  • #838 typed region and size errors, plus a public capabilities endpoint: ClickHouse/control-plane#44993.
  • #1154 phases 2–3: accept the CLI's token for database JWT exchange, or add a /v1 route: ClickHouse/control-plane#44995.
  • Upstream follow-ups to the ready CLI fixes: #824 → ClickHouse/control-plane#44988, #937 → ClickHouse/control-plane#44989, #926 → ClickHouse/control-plane#44990, #841 → ClickHouse/control-plane#44991, #835 → ClickHouse/control-plane#44992 (progress visibility), #931 → ClickHouse/control-plane#44994.
  • #923 waking a stopped service: the error should name the current state and the next command: ClickHouse/control-plane#45002.
  • #928 schema-assisted ClickPipe creation: the backend marks virtual fields, but the public API drops the flags: ClickHouse/control-plane#44998.

Blocked elsewhere

  • #276 Homebrew (PR #279): waiting on the macOS signing key.

Closed in this triage

  • Done: #757, #939, #1063 (#1076), #995 (#1115; the leftovers are noted on #1142), #254 (superseded by #1062)
  • Not planned: #832, #936, #929 (folded into #928), #206, #234

🤖 Generated with Claude Code

Dominant language
Rust
Stars
80
Forks
9
Avg merge
2d 18h
Merged PRs (30d)
51

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ClickHouse/clickhousectl

All issues in ClickHouse/clickhousectl

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.