@metabase/cli 0.1.6 → 0.1.8-alpha.cleanup-workspaces.75fe1d5

package/dist/url-DWaT6WIZ.mjs

@@ -1,56 +0,0 @@
-import "./command-augment-BH9qgQ5u.mjs";
-import { outputFlags } from "./error-C9S6PN3-.mjs";
-import { defineMetabaseCommand, localUrl } from "./runtime-Dmv5VtUK.mjs";
-import "./capabilities-7e9MgquN.mjs";
-import { renderScalar } from "./render-CfznwleY.mjs";
-import { parseId } from "./parse-id-lk_K-CEF.mjs";
-import "./poll-DHKDpCiq.mjs";
-import "./process-C7V8LJ-j.mjs";
-import { checkDockerReady, requireWorkspaceContainerLocation } from "./docker-Oq80q3tu.mjs";
-import { z } from "zod";
-
-//#region src/commands/workspace/url.ts
-const UrlResult = z.object({
-	workspace_id: z.number().int().positive(),
-	url: z.string()
-});
-const urlResultView = {
-	compactPick: UrlResult,
-	tableColumns: [{
-		key: "workspace_id",
-		label: "ID"
-	}, {
-		key: "url",
-		label: "URL"
-	}]
-};
-var url_default = defineMetabaseCommand({
-	meta: {
-		name: "url",
-		description: "Print the local URL the workspace's container is bound to"
-	},
-	capabilities: null,
-	args: {
-		...outputFlags,
-		id: {
-			type: "positional",
-			description: "Workspace id",
-			required: true
-		}
-	},
-	outputSchema: UrlResult,
-	examples: ["mb workspace url 1", "mb workspace url 1 --json"],
-	async run({ args, ctx }) {
-		const workspaceId = parseId(args.id);
-		await checkDockerReady();
-		const { hostPort } = await requireWorkspaceContainerLocation(workspaceId);
-		const result = {
-			workspace_id: workspaceId,
-			url: localUrl(hostPort)
-		};
-		renderScalar(result, urlResultView, result.url, ctx);
-	}
-});
-
-//#endregion
-export { url_default as default };

package/dist/values-BfSTAbzc.mjs

@@ -1,37 +0,0 @@
-import "./command-augment-BH9qgQ5u.mjs";
-import { connectionFlags, outputFlags, profileFlag } from "./error-C9S6PN3-.mjs";
-import { defineMetabaseCommand } from "./runtime-Dmv5VtUK.mjs";
-import "./capabilities-7e9MgquN.mjs";
-import { renderItem } from "./render-CfznwleY.mjs";
-import { FieldValues, fieldValuesView } from "./field-yomXlkvl.mjs";
-import { parseId } from "./parse-id-lk_K-CEF.mjs";
-
-//#region src/commands/field/values.ts
-var values_default = defineMetabaseCommand({
-	meta: {
-		name: "values",
-		description: "Fetch the cached distinct values for a field (FieldValues list)"
-	},
-	capabilities: { minVersion: 58 },
-	args: {
-		...outputFlags,
-		...profileFlag,
-		...connectionFlags,
-		id: {
-			type: "positional",
-			description: "Field id",
-			required: true
-		}
-	},
-	outputSchema: FieldValues,
-	examples: ["mb field values 100", "mb field values 100 --json"],
-	async run({ args, ctx, getClient }) {
-		const id = parseId(args.id);
-		const client = await getClient();
-		const values = await client.requestParsed(FieldValues, `/api/field/${id}/values`);
-		renderItem(values, fieldValuesView, ctx);
-	}
-});
-
-//#endregion
-export { values_default as default };

package/dist/wait-8yV9_WIo.mjs

@@ -1,19 +0,0 @@
-import { pollUntil } from "./poll-DHKDpCiq.mjs";
-import { Workspace } from "./workspace-BBXJczJK.mjs";
-
-//#region src/commands/workspace/database/wait.ts
-async function waitForDatabaseProvisioned(client, workspaceId, databaseId, schedule) {
-	return pollUntil(() => client.requestParsed(Workspace, `/api/ee/workspace-manager/${workspaceId}`), (workspace) => {
-		const entry = workspace.databases?.find((row) => row.database_id === databaseId);
-		return entry !== void 0 && entry.status === "provisioned";
-	}, schedule);
-}
-async function waitForDatabaseGone(client, workspaceId, databaseId, schedule) {
-	await pollUntil(() => client.requestParsed(Workspace, `/api/ee/workspace-manager/${workspaceId}`), (workspace) => {
-		const entry = workspace.databases?.find((row) => row.database_id === databaseId);
-		return entry === void 0;
-	}, schedule);
-}
-
-//#endregion
-export { waitForDatabaseGone, waitForDatabaseProvisioned };

package/dist/workspace-BBXJczJK.mjs

@@ -1,72 +0,0 @@
-import { z } from "zod";
-
-//#region src/domain/workspace.ts
-const WorkspaceDatabaseStatus = z.enum([
-	"unprovisioned",
-	"provisioning",
-	"provisioned",
-	"deprovisioning"
-]);
-const WorkspaceDatabase = z.object({
-	database_id: z.number().int(),
-	output_namespace: z.string(),
-	input_schemas: z.array(z.string().min(1)),
-	status: WorkspaceDatabaseStatus
-}).loose();
-const WorkspaceCreator = z.object({
-	id: z.number().int(),
-	first_name: z.string().nullable(),
-	last_name: z.string().nullable(),
-	email: z.string(),
-	common_name: z.string().nullable().optional()
-}).loose();
-const Workspace = z.object({
-	id: z.number().int(),
-	name: z.string(),
-	creator: WorkspaceCreator.nullable(),
-	created_at: z.string(),
-	updated_at: z.string(),
-	databases: z.array(WorkspaceDatabase).optional()
-}).loose();
-const WorkspaceCompact = Workspace.pick({
-	id: true,
-	name: true,
-	databases: true
-}).strip();
-const WorkspaceDatabaseList = z.array(WorkspaceDatabase);
-const workspaceView = {
-	compactPick: WorkspaceCompact,
-	tableColumns: [
-		{
-			key: "id",
-			label: "ID"
-		},
-		{
-			key: "name",
-			label: "Name"
-		},
-		{
-			key: "databases",
-			label: "Databases",
-			format: (value) => formatDatabases(value)
-		}
-	]
-};
-const WorkspaceCreateInput = z.object({ name: z.string().min(1) }).loose();
-const WorkspaceProvisionInput = z.object({
-	database_id: z.number().int().positive(),
-	input_schemas: z.array(z.string().min(1)).min(1)
-}).loose();
-const WorkspaceUpdateDatabaseInput = z.object({ input_schemas: z.array(z.string().min(1)).min(1) }).loose();
-function formatDatabases(value) {
-	if (value === void 0) return "";
-	const parsed = WorkspaceDatabaseList.safeParse(value);
-	if (!parsed.success || parsed.data.length === 0) return "(none)";
-	return parsed.data.map((entry) => {
-		const schemas = entry.input_schemas.length === 0 ? "" : ` [${entry.input_schemas.join(", ")}]`;
-		return `${entry.database_id} (${entry.status})${schemas}`;
-	}).join("; ");
-}
-
-//#endregion
-export { Workspace, WorkspaceCompact, WorkspaceCreateInput, WorkspaceProvisionInput, WorkspaceUpdateDatabaseInput, workspaceView };

package/dist/workspace-CKLZrR7l.mjs

@@ -1,26 +0,0 @@
-import { defineCommand } from "citty";
-
-//#region src/commands/workspace/index.ts
-var workspace_default = defineCommand({
-	meta: {
-		name: "workspace",
-		alias: "workspaces",
-		description: "Manage Metabase workspaces (workspace-manager)"
-	},
-	subCommands: {
-		list: () => import("./list-zSO0DMw-.mjs").then((mod) => mod.default),
-		create: () => import("./create-CHF313Qg.mjs").then((mod) => mod.default),
-		database: () => import("./database-CIXwHKjK.mjs").then((mod) => mod.default),
-		start: () => import("./start-3PX3ahjT.mjs").then((mod) => mod.default),
-		stop: () => import("./stop-CQ0XGrN8.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-CM3jnAeQ.mjs").then((mod) => mod.default),
-		logs: () => import("./logs-CywPikkL.mjs").then((mod) => mod.default),
-		url: () => import("./url-DWaT6WIZ.mjs").then((mod) => mod.default),
-		credentials: () => import("./credentials-dzeq7ckm.mjs").then((mod) => mod.default),
-		ps: () => import("./ps-DEroLgbI.mjs").then((mod) => mod.default),
-		license: () => import("./license-Dxarh-gG.mjs").then((mod) => mod.default)
-	}
-});
-
-//#endregion
-export { workspace_default as default };

package/dist/workspace-credentials-BXpABsNZ.mjs

@@ -1,100 +0,0 @@
-import { ConfigError } from "./command-augment-BH9qgQ5u.mjs";
-import { parseYaml, stringifyYaml } from "./yaml-YTQiYJ9s.mjs";
-import { z } from "zod";
-import { randomBytes } from "node:crypto";
-
-//#region src/core/workspace-credentials.ts
-const API_KEY_NAME = "Workspace API Key";
-const API_KEY_GROUP = "admin";
-const PASSWORD_BYTE_LENGTH = 18;
-const API_KEY_BYTE_LENGTH = 32;
-const WorkspaceCredentials = z.object({
-	workspace_id: z.number().int().positive(),
-	user: z.object({
-		first_name: z.string().min(1),
-		last_name: z.string().min(1),
-		password: z.string().min(1),
-		email: z.string().min(1)
-	}),
-	api_key: z.object({
-		name: z.string().min(1),
-		group: z.enum(["admin", "all-users"]),
-		creator: z.string().min(1),
-		key: z.string().regex(/^mb_[A-Za-z0-9+/=]+$/)
-	})
-});
-function generateWorkspaceCredentials(workspaceId) {
-	const email = `workspace-${workspaceId}@workspace.local`;
-	return {
-		workspace_id: workspaceId,
-		user: {
-			first_name: "Workspace",
-			last_name: "Admin",
-			password: randomBase64Url(PASSWORD_BYTE_LENGTH),
-			email
-		},
-		api_key: {
-			name: API_KEY_NAME,
-			group: API_KEY_GROUP,
-			creator: email,
-			key: `mb_${randomBytes(API_KEY_BYTE_LENGTH).toString("base64")}`
-		}
-	};
-}
-const credentialsJsonEncoder = new TextEncoder();
-function buildCredentialsJson(credentials) {
-	return credentialsJsonEncoder.encode(`${JSON.stringify(credentials, null, 2)}\n`);
-}
-const ConfigEnvelopeShape = z.object({
-	version: z.number().int(),
-	config: z.looseObject({})
-}).loose();
-function injectCredentialsIntoConfig(yamlInput, credentials) {
-	const envelope = parseYaml(yamlInput, ConfigEnvelopeShape, { source: "config.yml" });
-	if ("users" in envelope.config || "api-keys" in envelope.config) throw new ConfigError("config.yml already declares users or api-keys — refusing to overwrite parent-supplied credentials");
-	const merged = {
-		...envelope,
-		config: {
-			...envelope.config,
-			users: [credentials.user],
-			"api-keys": [credentials.api_key]
-		}
-	};
-	return stringifyYaml(merged);
-}
-const REPO_SYNC_MODES = ["read-write", "read-only"];
-const RepoSyncMode = z.enum(REPO_SYNC_MODES);
-const ConfigEnvelopeWithSettingsShape = z.object({
-	version: z.number().int(),
-	config: z.object({ settings: z.looseObject({}).optional() }).loose()
-}).loose();
-const REMOTE_SYNC_KEYS = [
-	"remote-sync-url",
-	"remote-sync-branch",
-	"remote-sync-type"
-];
-function injectRepoSettingsIntoConfig(yamlInput, repo) {
-	const envelope = parseYaml(yamlInput, ConfigEnvelopeWithSettingsShape, { source: "config.yml" });
-	const existingSettings = envelope.config.settings ?? {};
-	const conflicts = REMOTE_SYNC_KEYS.filter((key) => key in existingSettings);
-	if (conflicts.length > 0) throw new ConfigError(`config.yml already declares remote-sync settings (${conflicts.join(", ")}) — refusing to overwrite parent-supplied values`);
-	const merged = {
-		...envelope,
-		config: {
-			...envelope.config,
-			settings: {
-				...existingSettings,
-				"remote-sync-url": repo.url,
-				"remote-sync-branch": repo.branch,
-				"remote-sync-type": repo.mode
-			}
-		}
-	};
-	return stringifyYaml(merged);
-}
-function randomBase64Url(byteLength) {
-	return randomBytes(byteLength).toString("base64url");
-}
-
-//#endregion
-export { REPO_SYNC_MODES, RepoSyncMode, WorkspaceCredentials, buildCredentialsJson, generateWorkspaceCredentials, injectCredentialsIntoConfig, injectRepoSettingsIntoConfig };

package/dist/yaml-YTQiYJ9s.mjs

@@ -1,43 +0,0 @@
-import { ConfigError, ValidationError, errorMessage } from "./command-augment-BH9qgQ5u.mjs";
-import { YAMLParseError, parse, stringify } from "yaml";
-
-//#region src/runtime/yaml.ts
-function parseYaml(input, schema, opts = {}) {
-	const result = parseYamlResult(input, schema, opts);
-	if (!result.ok) throw result.error;
-	return result.value;
-}
-function parseYamlResult(input, schema, opts = {}) {
-	const sourcePrefix = opts.source ? `${opts.source}: ` : "";
-	let raw;
-	try {
-		raw = parse(input);
-	} catch (error) {
-		if (error instanceof YAMLParseError) return {
-			ok: false,
-			error: new ConfigError(`${sourcePrefix}invalid YAML: ${error.message}`)
-		};
-		return {
-			ok: false,
-			error: new ConfigError(`${sourcePrefix}invalid YAML: ${errorMessage(error)}`)
-		};
-	}
-	const parsed = schema.safeParse(raw);
-	if (!parsed.success) return {
-		ok: false,
-		error: new ValidationError(`${sourcePrefix}value did not match expected schema`, {
-			source: opts.source ?? "<input>",
-			zodIssues: parsed.error.issues
-		})
-	};
-	return {
-		ok: true,
-		value: parsed.data
-	};
-}
-function stringifyYaml(value) {
-	return stringify(value, { lineWidth: 0 });
-}
-
-//#endregion
-export { parseYaml, parseYamlResult, stringifyYaml };

package/skill-data/viz/SKILL.md

@@ -1,137 +0,0 @@
----
-name: viz
-description: Author Metabase `visualization_settings` and pick the right `display` for cards via the `mb` CLI. Covers the display → settings-namespace map (graph.*, pie.*, funnel.*, scalar.*, table.*, …), the column-name-vs-numeric-field-id rule, the `column_settings` JSON-string-key footgun, worked API-form examples per chart family, and the pull-from-UI escape hatch for complex charts. Load whenever shaping how a card renders by hand — "create a bar chart", "make this a line chart", "format this column as currency", "set the pie dimension and metric", "the card renders as a table instead of a chart", "add conditional formatting", or any `visualization_settings` work.
-allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
----
-
-# Visualization settings
-
-A card has two presentation fields alongside its `dataset_query`:
-
-- **`display`** — the chart type (`bar`, `line`, `pie`, `scalar`, `table`, …). One closed set of values; pick from the enum below.
-- **`visualization_settings`** — a free-form map whose keys are **namespaced by `display`** (`graph.*` for bar/line, `pie.*` for pie, …). The server stores almost anything and **silently ignores keys that don't apply** to the chosen `display`.
-
-The MBQL pre-flight does **not** validate `visualization_settings` — there is no `--skip-validate` to fail past, because nothing checks it. A `display` typo or a misnamed key is accepted by the API and the card just renders as a default table or drops the setting. So **the feedback loop is read-back, not pre-flight**: after `card create`/`update`, confirm with `mb card get <id> --full --json` (or open the card) that it rendered as intended.
-
-The general flag conventions and body-input precedence live in the `core` skill (`mb skills get core`); the `dataset_query` body itself is the `mbql` skill's job (`mb skills get mbql`). This skill is only about how the result is displayed.
-
-## `display` decides everything
-
-`display` selects which setting namespace is read. Pick `display` first, then only the matching namespace's keys matter.
-
-| `display`                                   | Settings namespace(s)                                     | Key columns are named by |
-| ------------------------------------------- | --------------------------------------------------------- | ------------------------ |
-| `bar` `line` `area` `combo` `row` `scatter` | `graph.*`, `series_settings`, `column_settings`           | output column **name**   |
-| `waterfall`                                 | `graph.*` + `waterfall.*`                                 | output column name       |
-| `boxplot`                                   | `graph.*` + `boxplot.*`                                   | output column name       |
-| `pie`                                       | `pie.*`, `column_settings`                                | output column name       |
-| `scalar` `number`                           | `scalar.*`                                                | output column name       |
-| `smartscalar`                               | `scalar.comparisons`                                      | output column name       |
-| `funnel`                                    | `funnel.*`                                                | output column name       |
-| `gauge`                                     | `gauge.*`                                                 | —                        |
-| `map`                                       | `map.*`                                                   | output column name       |
-| `pivot`                                     | `pivot_table.*`, `table.*`                                | output column name       |
-| `sankey`                                    | `sankey.*`                                                | output column name       |
-| `table`                                     | `table.*`, `column_settings`                              | output column name       |
-| `object` `list`                             | `column_settings`                                         | output column name       |
-| `progress`                                  | `progress.goal`, `progress.color` (sparse — pull from UI) | —                        |
-| `heading` `text` `link` `iframe` `action`   | dashcard-only `virtual_card` (see references)             | —                        |
-
-Closed `display` enum (card-level): `table`, `bar`, `line`, `area`, `row`, `pie`, `scalar`, `smartscalar`, `number`, `combo`, `pivot`, `funnel`, `map`, `scatter`, `waterfall`, `progress`, `gauge`, `object`, `list`, `sankey`, `boxplot`. (`heading`/`text`/`link`/`iframe`/`action` are dashcard virtuals, not standalone cards.) An unknown value is accepted by the API but renders nothing useful — typos like `bargraph`/`linechart` are the most common cause of a "why is my chart blank" report.
-
-## The rule that trips everyone: settings name **output columns**, by name
-
-`graph.dimensions`, `graph.metrics`, `pie.dimension`, `pie.metric`, `scalar.field`, `funnel.metric`, `map.latitude_column`, … all take **output column-name strings** — the names the query _produces_, not field ids. A `count` aggregation outputs the column `count`; a breakout on a field outputs that field's name; a named aggregation outputs its `name`. These strings are **identical in the API form and the portable (git-sync) form** — no numeric-vs-name footgun here.
-
-So the names you put in `visualization_settings` come from the query's output, not from `mb field`/`mb table`. If you set `name` on an aggregation (see the `mbql` skill, "Naming aggregation output columns"), use that same string here.
-
-## Minimum-viable settings per chart family (API form)
-
-Each example is the `visualization_settings` block to pair with the given `display` on a `card create`/`update` body. The `dataset_query` is elided — build it per the `mbql` skill. The output columns referenced (`CATEGORY`, `count`) are whatever the query's breakout/aggregation produce.
-
-**Bar / line / area** — one dimension on the x-axis, one or more metrics:
-
-```json
-"display": "bar",
-"visualization_settings": {
-  "graph.dimensions": ["CATEGORY"],
-  "graph.metrics": ["count"]
-}
-```
-
-(Switch `display` to `line` or `area` with the same `graph.*` keys. Multiple metrics: `"graph.metrics": ["count", "sum"]`. Stacked: add `"stackable.stack_type": "stacked"`.)
-
-**Pie** — one dimension, one metric:
-
-```json
-"display": "pie",
-"visualization_settings": { "pie.dimension": "CATEGORY", "pie.metric": "count" }
-```
-
-**Scalar** (single big number) — the field to surface:
-
-```json
-"display": "scalar",
-"visualization_settings": { "scalar.field": "count" }
-```
-
-**Table** — column order/visibility plus per-column formatting:
-
-```json
-"display": "table",
-"visualization_settings": {
-  "table.columns": [
-    { "name": "CATEGORY", "enabled": true },
-    { "name": "count", "enabled": true }
-  ],
-  "column_settings": {
-    "[\"name\",\"count\"]": { "column_title": "Orders" }
-  }
-}
-```
-
-An **empty** `"visualization_settings": {}` is valid for any `display` — Metabase falls back to sensible defaults (it auto-picks dimensions/metrics for a simple aggregate). Set keys only to override the defaults.
-
-## `column_settings`: the JSON-string-key footgun
-
-`column_settings` is a map **whose keys are themselves JSON-encoded arrays** — so inside a JSON body the inner quotes must be escaped. The key is a _string_, never an object.
-
-- **Prefer the name form:** `["name", "<output column name>"]` → in a JSON body, `"[\"name\",\"count\"]"`. This is the canonical key Metabase writes (`getColumnKey`), and it's **identical in API and portable form**. Use it unless you have a reason not to.
-- **Ref form (legacy order!):** `["ref", ["field", <id>, <opts>]]`. The inner field ref here uses the **legacy MBQL-4 order** `["field", id, options]` (id **second**) — _not_ the MBQL-5 order `["field", {options}, id]` you use in `dataset_query`. In the API form `<id>` is the **numeric** field id; the portable form uses a name path. Because the order differs from MBQL 5, this form is easy to get wrong — reach for the name form instead.
-
-```json
-"column_settings": {
-  "[\"name\",\"TOTAL\"]": { "number_style": "currency", "currency": "USD", "decimals": 2 },
-  "[\"name\",\"CREATED_AT\"]": { "date_style": "MMMM D, YYYY" }
-}
-```
-
-The exhaustive per-column key list (number/date/link formatting, `view_as`, click behavior) is in the references file.
-
-## Escape hatch: pull a real card instead of authoring from scratch
-
-For anything beyond a single dimension + metric — combo charts, conditional formatting, pivot splits, click behavior, series colors — the cheapest **correct** path is to build it once in the Metabase UI and copy the result:
-
-```bash
-mb card get <id> --full --json | jq '.visualization_settings'
-```
-
-Paste that block into your `card create`/`update` body. The server produced it, so it's guaranteed valid for that `display`. This beats guessing keys from memory, and it's token-cheap (no schema dump).
-
-## Full key catalog
-
-The body above covers the high-frequency 90%. The complete per-display key tables — every `graph.*`/`pie.*`/`table.*`/… key, series settings, conditional formatting rules, pivot splits, the full `column_settings` formatting vocabulary, virtual-card (heading/text/link/iframe) settings, and click behavior — live in this skill's references file. Load it on demand, not by default:
-
-```bash
-mb skills get viz --full          # appends references/settings.md to this body
-mb skills path viz                # → the skill dir; then Read references/settings.md
-```
-
-## Don't
-
-- Don't invent `display` values (`bargraph`, `linechart`, `histogram`) — use the closed enum; the API accepts the typo and renders nothing.
-- Don't put numeric field ids in `graph.dimensions`/`pie.metric`/`scalar.field` etc. — they take **output column-name strings**.
-- Don't write a `column_settings` key as an object — it's a JSON **string** (`"[\"name\",\"COL\"]"`), inner quotes escaped.
-- Don't use the MBQL-5 field-ref order inside a `column_settings` `["ref", …]` key — that key uses the **legacy** `["field", id, opts]` order. Prefer the `["name", …]` form and sidestep it.
-- Don't expect a pre-flight to catch viz mistakes — there is none. Verify by reading the card back.
-- Don't hand-author complex charts when you can pull a working `visualization_settings` from a UI-built card.