Context
Discovered while auditing 14 Keboola projects for a single question: "Which Snowflake writers are active, part of a scheduled flow, and load a source table larger than 1 GB in full-load mode?" The audit should be answerable end-to-end from the CLI / MCP tools, but several gaps forced manual workarounds. This issue covers one of them; the audit uncovered three more, filed separately.
Problem
config detail returns one config at a time. When an audit needs rows + state for many configs (e.g. all writers of a given component across the fleet), the only option is N parallel CLI invocations. For 102 Snowflake writers this meant 102 subprocesses; at fleet-scale (thousands of configs) this will not be viable.
Workaround used
Shell script fanning out 102 background kbagent config detail calls and collecting JSON files in /tmp.
Use case
Audits across an entire organization's configs (compliance checks, "which configs use deprecated parameter X", onboarding checklists). Without a bulk path, users hit rate limits and complicated parallel orchestration for what is conceptually one question.
Context
Discovered while auditing 14 Keboola projects for a single question: "Which Snowflake writers are active, part of a scheduled flow, and load a source table larger than 1 GB in full-load mode?" The audit should be answerable end-to-end from the CLI / MCP tools, but several gaps forced manual workarounds. This issue covers one of them; the audit uncovered three more, filed separately.
Problem
config detailreturns one config at a time. When an audit needs rows + state for many configs (e.g. all writers of a given component across the fleet), the only option is N parallel CLI invocations. For 102 Snowflake writers this meant 102 subprocesses; at fleet-scale (thousands of configs) this will not be viable.Workaround used
Shell script fanning out 102 background
kbagent config detailcalls and collecting JSON files in/tmp.Use case
Audits across an entire organization's configs (compliance checks, "which configs use deprecated parameter X", onboarding checklists). Without a bulk path, users hit rate limits and complicated parallel orchestration for what is conceptually one question.