Skip to content

Align ClickHouse data analyst Cloud access with direct Query API#222

Open
alex-lum wants to merge 4 commits into
mainfrom
clickhouse-data-analyst-direct-query-api
Open

Align ClickHouse data analyst Cloud access with direct Query API#222
alex-lum wants to merge 4 commits into
mainfrom
clickhouse-data-analyst-direct-query-api

Conversation

@alex-lum

Copy link
Copy Markdown

Summary

  • update the ClickHouse data analyst skill to use the configured direct ClickHouse Query API endpoint for Cloud analytics
  • require per-user CH_API_KEY / CH_API_SECRET credentials authorized on the Prod Query API endpoint
  • explicitly avoid ClickHouse MCP tools and clickhousectl cloud service query for Cloud analytics to prevent local service-query-key dependency and key sprawl
  • keep clickhousectl local client as the local/host-port path

Validation

  • git diff --check
  • git diff --check origin/main...HEAD
  • npm run validate

alex-lum added 4 commits June 22, 2026 12:07
Replace clickhousectl cloud service query with the direct ClickHouse
Query API (CH_API_KEY / CH_API_SECRET via curl) for Cloud analytics.

- data-analyst/SKILL.md: add explicit note that Cloud queries use the
  direct Query API, not clickhousectl cloud service query
- skills/clickhouse/SKILL.md: rewrite to document two access paths:
  Path A (Cloud) = direct Query API via curl
  Path B (local/host-port) = clickhousectl local client
  Remove clickhousectl cloud auth and cloud service query from the
  Cloud workflow entirely

Fixes the FORBIDDEN provisioning error on first use and removes the
admin-key requirement for new users.
…in SKILL.md

Convert bold markdown formatting (`**text**`) and em-dash separators (`—`) to plain text and hyphens (`-`) in list items across SKILL.md files for improved compatibility and readability.
…Cloud analytics

Replace direct Query API usage with `clickhousectl cloud service query`
using explicit per-user API key/secret credentials for ClickHouse Cloud
analytics. Restrict `CH_QUERY_API_URL` usage to only when users explicitly
provide a saved-query endpoint URL for preconfigured queries. Update README,
SKILL.md, and clickhouse sub-skill docs to reflect the new recommended
workflow and remove references to the old direct Query API approach.
… API endpoint

Replace `clickhousectl cloud service query` with the configured direct
ClickHouse Query API endpoint for Cloud analytics workflows. The previous
approach relied on local service-query-key state and could auto-provision
keys, which is undesirable. Update README, SKILL.md, and clickhouse skill
docs to reflect the new preferred path using per-user `CH_API_KEY` /
`CH_API_SECRET` credentials against the configured Query API URL directly.
@alex-lum alex-lum requested a review from saoudrizwan June 29, 2026 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant