@metabase/cli 0.3.0-alpha.extract-api-client.e9b2dd5 → 0.3.1

package/dist/upload-CEGVxmYB.mjs

@@ -0,0 +1,42 @@
+import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-z8rra6-I.mjs";
+import { t as ContentTranslationUploadResult } from "./content-translation-BrHOrmj9.mjs";
+import { n as requireUploadFilePath, t as readCsvFile } from "./upload-CD555ui1.mjs";
+//#region src/output/views/content-translation.ts
+const contentTranslationUploadView = {
+	compactPick: ContentTranslationUploadResult,
+	tableColumns: [{
+		key: "success",
+		label: "Success"
+	}]
+};
+//#endregion
+//#region src/commands/content-translation/upload.ts
+var upload_default = defineMetabaseCommand({
+	meta: {
+		name: "upload",
+		description: "Replace the complete content translation dictionary from CSV"
+	},
+	details: "Uploads one complete dictionary and replaces every active content translation on the server. Keep the canonical full CSV in version control and download the current dictionary before replacing it. Metabase accepts dictionaries up to 1.5 MiB.",
+	capabilities: {
+		minVersion: 58,
+		tokenFeature: "content_translation"
+	},
+	args: {
+		...outputFlags,
+		...profileFlag,
+		...connectionFlags,
+		file: {
+			type: "string",
+			description: "Path to the complete translation dictionary CSV"
+		}
+	},
+	outputSchema: ContentTranslationUploadResult,
+	examples: ["mb content-translation upload --file translations.csv", "mb content-translation upload --file translations.csv --profile prod --json"],
+	async run({ args, ctx, getClient }) {
+		const file = await readCsvFile(requireUploadFilePath(args.file));
+		renderSummary(await (await getClient()).contentTranslation.upload(file), contentTranslationUploadView, `Replaced the content translation dictionary with "${file.filename}".`, ctx);
+	}
+});
+//#endregion
+export { upload_default as default };

package/dist/{upload-Dey_8rLf.mjs → upload-DsYCf5kB.mjs}

@@ -4,9 +4,9 @@ var upload_default = defineCommandGroup({
 	name: "upload",
 	description: "Upload CSV files into Metabase",
 	subCommands: {
-		csv: () => import("./csv-B2Jgb1GM.mjs").then((m) => m.default),
-		append: () => import("./append-DFzQRPMd.mjs").then((m) => m.default),
-		replace: () => import("./replace-Cq4CxVa-.mjs").then((m) => m.default)
+		csv: () => import("./csv-BLPJtlSC.mjs").then((m) => m.default),
+		append: () => import("./append-Bl_Ensmr.mjs").then((m) => m.default),
+		replace: () => import("./replace-CtsWICrD.mjs").then((m) => m.default)
 	}
 });
 //#endregion

package/dist/{uuid-BJkDWj9p.mjs → uuid-C4hqn3kA.mjs}

@@ -1,6 +1,6 @@
 import { i as ConfigError } from "./predicates-Bkm2IoeX.mjs";
 import { F as outputFlags, l as writeJson, u as writeText } from "./cli.mjs";
-import { R as parseInteger, t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
+import { R as parseInteger, t as defineMetabaseCommand } from "./runtime-z8rra6-I.mjs";
 import { z } from "zod";
 import { randomUUID } from "node:crypto";
 //#region src/commands/uuid.ts

package/dist/{values-Dxf1JEoA.mjs → values-C0O3eNaW.mjs}

@@ -1,6 +1,6 @@
 import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary, f as formatScalar } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
+import { t as defineMetabaseCommand } from "./runtime-z8rra6-I.mjs";
+import { t as parseId } from "./parse-id-B3YwNojT.mjs";
 import { s as FieldValues } from "./field-Cr2DPUG9.mjs";
 import { n as fieldValuesView } from "./field-BPsNa-TO.mjs";
 //#region src/commands/field/values.ts

package/dist/{verify-K96rItG5.mjs → verify-DfTjYF7s.mjs}

@@ -1,7 +1,7 @@
-import { n as createClient } from "./client-BqhzKdLM.mjs";
+import { n as createClient } from "./client-mKuHg_sc.mjs";
 import { f as errorMessage, l as TimeoutError, o as MetabaseError, s as NetworkError } from "./predicates-Bkm2IoeX.mjs";
-import { F as tryParseTag, I as SessionProperties, u as USER_AGENT } from "./runtime-DiKyBxOw.mjs";
-import { r as HttpError } from "./network-error-CEb9ymDW.mjs";
+import { F as tryParseTag, I as SessionProperties, u as USER_AGENT } from "./runtime-z8rra6-I.mjs";
+import { r as HttpError } from "./network-error-D6CiOEBw.mjs";
 //#region ../client/src/version/probe.ts
 const PROBE_PATH = "/api/session/properties";
 const PROBE_TIMEOUT_MS = 1e4;

package/dist/{wait-DoMDH226.mjs → wait-WZmFenN_.mjs}

@@ -1,7 +1,7 @@
 import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
+import { t as defineMetabaseCommand } from "./runtime-z8rra6-I.mjs";
 import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-75SvT7Zv.mjs";
-import { r as parseWaitSchedule } from "./wait-flags-DWEF9tX4.mjs";
+import { r as parseWaitSchedule } from "./wait-flags-BbfDSP8R.mjs";
 import { c as syncTaskView } from "./git-sync-DxD_ng48.mjs";
 import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask, r as syncTaskIdleView, t as SyncTaskOrIdle } from "./sync-task-BACcrs0i.mjs";
 //#region src/commands/git-sync/wait.ts

package/dist/{wait-flags-DWEF9tX4.mjs → wait-flags-BbfDSP8R.mjs}

@@ -1,5 +1,5 @@
 import { t as interruptSignal } from "./cli.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
+import { t as parseId } from "./parse-id-B3YwNojT.mjs";
 import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-75SvT7Zv.mjs";
 //#region src/commands/wait-flags.ts
 const waitScheduleFlags = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/cli",
-  "version": "0.3.0-alpha.extract-api-client.e9b2dd5",
+  "version": "0.3.1",
   "description": "Metabase CLI",
   "license": "AGPL-3.0",
   "repository": {

package/skill-data/core/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: core
-description: Foundations for driving Metabase from the terminal with the `mb` CLI — authentication and named profiles, the flag/output/`--json` conventions every command shares, JSON body input, command discovery via `--help` (add `--json` for machine-readable schemas), and the per-resource footguns (db, table, field, upload, card, dashboard, collection, segment, measure, timeline, alert, subscription, library, setting, search, eid). Load first for any `mb` task; it routes to the specialized skills for deeper work.
+description: Foundations for driving Metabase from the terminal with the `mb` CLI — authentication and named profiles, the flag/output/`--json` conventions every command shares, JSON body input, command discovery via `--help` (add `--json` for machine-readable schemas), and the per-resource footguns (db, table, field, upload, content translation, card, dashboard, collection, segment, measure, timeline, alert, subscription, library, setting, search, eid). Load first for any `mb` task; it routes to the specialized skills for deeper work.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
 ---
 
@@ -11,7 +11,7 @@ The official Metabase CLI (`mb`) drives a Metabase instance over its REST API: a
 Top-level command groups (run `mb <group> --help` to discover verbs):
 
 ```
-auth | db | table | field | upload | query | card | dashboard | snippet | segment | measure | collection | library
+auth | db | table | field | upload | content-translation | query | card | dashboard | snippet | segment | measure | collection | library
 document | timeline | timeline-event | transform | transform-job | transform-tag | alert | subscription | setting
 search | git-sync | setup | eid | uuid | upgrade | skills
 ```
@@ -129,8 +129,9 @@ Routine verb shapes (list / get / create / update), every flag, and output schem
 - **table fields.** `table get` never returns fields on its own — pass `--include fields` (compact; the underlying query_metadata response also carries FK targets and dimensions, visible under `--full`) or use `table fields <id>` (list envelope). `table update` patches table-level metadata only; physical columns aren't editable.
 - **field has no `list`.** Fields are per-table — get them via `table get <id> --include fields`. Never enumerate fields across a whole db (context blow-up). `field summary` is live cardinality `{field_id, count, distincts}`; `field values` is the cached distinct set (`has_more_values: true` ⇒ truncated cache). `field update` patches metadata only (`base_type` isn't editable) — this is where you set a column's `semantic_type` or foreign-key target.
 - **upload (CSV → tables).** `upload csv --file <path>` creates a new table + model (prints `{model_id, table_id}`); `upload append <table-id>` / `upload replace <table-id> --file <path>` add to / overwrite a table **previously created by upload** (columns must match). The destination db+schema is admin-configured, not per-call — check with `mb setting get uploads-settings --json` (`db_id: null` ⇒ uploads off/unconfigured; needs admin to read). `--collection <id|root>` only sets the model's collection. Max 50 MB. Errors: **"The uploads database is not configured."** = no db has uploads enabled; **"Uploads are not enabled."** = the append/replace target isn't an uploaded table.
+- **content-translation.** EE-only (`content_translation` premium feature), admin-only, and separate from Remote Sync. `content-translation download > translations.csv` streams the complete active dictionary; `content-translation upload --file translations.csv` replaces every active translation with the file's contents. Always upload the canonical complete CSV, never a partial patch. An empty dictionary downloads as Metabase's four-row sample dictionary — don't re-upload it as real translations. Metabase limits dictionaries to 1.5 MiB.
 - **card.** `dataset_query` is the **flat** `mbql/query` value, not a legacy `{type:"query",query:…}` envelope (→ `mbql`). `--export-format csv|xlsx` streams the raw export (pipe to a file), bypassing the JSON envelope. `archive` is the only delete; unarchive with `update --body '{"archived":false}'`. `visualization_settings` keys are scoped by `display` and aren't pre-flighted — see `visualization`.
-- **dashboard.** Dashcards round-trip through `PUT /api/dashboard/:id` (no per-dashcard endpoint): `update-dashcard <dash-id> <dashcard-id>` patches one safely; `update --body '{"dashcards":[…]}'` replaces the whole set (omitted ids are deleted server-side; negative ids for new cards). `create` accepts the **same** `dashcards` array in its initial body — lay out the whole dashboard in one call: negative ids for new cards, and `card_id:null` plus a `visualization_settings.virtual_card` block (`{display:"text"|"heading"|"link"|…}`) for non-question cards. `create`/`update` pre-flight every positive `card_id` and exit **2** with `{ok:false,errors:[…]}` on a bad ref (non-bypassable). `dashboard get <id>` (or `--full`) hydrates dashcards/tabs; `list` omits them. **The grid is 24 columns wide:** each dashcard's `{col, row, size_x, size_y}` is in grid units — **full-width is `size_x: 24`** (`size_x: 12` is half a row, the usual cause of a card filling only half the width). Keep `col + size_x ≤ 24`, start a full-width stack's `col` at 0, and don't overlap (the server stores collisions as sent — no auto-fix). Layout patterns and per-chart default sizes → the `dashboard` skill; load it before composing any `dashcards` array.
+- **dashboard.** Dashcards round-trip through `PUT /api/dashboard/:id` (no per-dashcard endpoint): `update-dashcard <dash-id> <dashcard-id>` patches one safely; `update --body '{"dashcards":[…]}'` replaces the whole set (omitted ids are deleted server-side; negative ids for new cards). Every dashcard must include `card_id`, including existing rows; use `card_id:null` plus a `visualization_settings.virtual_card` block (`{display:"text"|"heading"|"link"|…}`) for non-question cards. `create` accepts the **same** `dashcards` array in its initial body, so lay out the whole dashboard in one call. `create`/`update` pre-flight every positive `card_id` and exit **2** with `{ok:false,errors:[…]}` on a bad ref (non-bypassable). `dashboard get <id>` (or `--full`) hydrates dashcards/tabs; `list` omits them. **The grid is 24 columns wide:** each dashcard's `{col, row, size_x, size_y}` is in grid units — **full-width is `size_x: 24`** (`size_x: 12` is half a row, the usual cause of a card filling only half the width). Keep `col + size_x ≤ 24`, start a full-width stack's `col` at 0, and don't overlap (the server stores collisions as sent — no auto-fix). Layout patterns and per-chart default sizes → the `dashboard` skill; load it before composing any `dashcards` array.
 - **dashboard parameters (filters).** A dashboard's `parameters` array holds its filter widgets; they're part of the dashboard record, so read them with `dashboard get <id> --fields parameters --json` (no separate verb). **Editing replaces the _whole_ array** (like dashcards), so it's a read-modify-write loop and omitting a parameter deletes it. A parameter only filters a card once it is **mapped** onto that dashcard's `parameter_mappings` — an unmapped parameter is an inert widget. `type` is a **closed enum**; an unlisted value is a hard parse error that echoes the full allowed set back to you. `dashboard parameter-values <id> <parameter-id> [--query <substr>]` fetches a widget's selectable values (`{values, has_more_values}`; `--query` is a case-insensitive substring search). Parameter types, ids, mapping targets, and value sources → the `dashboard` skill; load it before authoring a `parameters` array.
 - **alert / subscription are two unrelated systems.** `alert` watches one **card** and fires on a send condition (`/api/notification`: a cron string, `channel/email`-prefixed handlers, typed recipients); `subscription` delivers one **dashboard** on a schedule (`/api/pulse`: structured `schedule_type` + hour/day/frame, bare `email` channels, `{id}|{email}` recipients). The bodies are not interchangeable. Both silently deliver nowhere if the server has no SMTP / Slack app — check `mb setting get 'email-configured?'` (quote it; the `?` is a shell glob) before creating either. Their list-valued fields (`handlers`/`subscriptions`, `channels`/`cards`) **replace wholesale** on update, so adding one recipient is a read-modify-write. `mb card alerts <id>` and `mb dashboard subscriptions <id>` list what's already attached to a card/dashboard; `archive` deactivates rather than deletes. Load the `notification` skill before authoring either body.
 - **snippet `--archived` is a swap, not a union** — list returns _either_ active _or_ archived rows, never both. (Same for `--filter archived` on dashboard/collection.)

package/skill-data/dashboard/SKILL.md

@@ -8,7 +8,7 @@ allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
 
 A dashboard starts as cards on a grid; it becomes an **app** when filters drive the cards, charts cross-filter each other, and clicks navigate. This skill owns both: the grid layout and the interactive layer.
 
-**`core` owns the transport mechanics** — the whole-array replace semantics (editing `dashcards` or `parameters` replaces the entire set; omitted entries are deleted; new cards use negative ids), `update-dashcard` for a single safe patch vs. `update --body` for a full replace, and the `parameter-values` verb. Read it first (`mb skills get core`). **`visualization`** owns each card's chart and the full `click_behavior` key catalog.
+**`core` owns the transport mechanics** — the whole-array replace semantics (editing `dashcards` or `parameters` replaces the entire set; omitted entries are deleted; every dashcard carries `card_id`, with `null` for virtual cards; new cards use negative ids), `update-dashcard` for a single safe patch vs. `update --body` for a full replace, and the `parameter-values` verb. Read it first (`mb skills get core`). **`visualization`** owns each card's chart and the full `click_behavior` key catalog.
 
 Inspect before you wire: `mb dashboard get <id> --json` hydrates `parameters`, `dashcards`, and `tabs`; `mb dashboard cards <id>` lists just the dashcards.
 
@@ -123,7 +123,7 @@ Set the **driver** chart's whole-card click behavior to `crossfilter`, mapping t
 - **Auto-connect / the missing map:** a filter that "does nothing" or "won't show" is almost always unmapped, or mapped only to cards on another tab.
 - **Time-grouping parameters** (`temporal-unit`) bind only to a datetime column in the query's **last** stage — add one after a time-bucketed summary and it can't attach.
 - **Required + default:** a `required: true` parameter with no `default` blocks its cards until a value is chosen; give it a `default` for expensive queries you don't want running unfiltered.
-- **Whole-array replace:** never send a partial `parameters`/`dashcards` array to `update` — you'll delete what you omit. Use `update-dashcard` for a single-card change.
+- **Whole-array replace:** never send a partial `parameters`/`dashcards` array to `update` — you'll delete what you omit. Include `card_id` on every dashcard (`null` for virtual cards). Use `update-dashcard` for a single-card change.
 
 ## Don't
 

package/dist/git-sync-MQQYRYLg.mjs

@@ -1,28 +0,0 @@
-import { t as defineCommandGroup } from "./group-DBM87IgC.mjs";
-//#region src/commands/git-sync/index.ts
-var git_sync_default = defineCommandGroup({
-	name: "git-sync",
-	description: "Sync Metabase content with a git remote",
-	skills: [{
-		skill: "git-sync",
-		purpose: "import/export round-trip and dirty checks"
-	}],
-	subCommands: {
-		status: () => import("./status-BhswxJL1.mjs").then((mod) => mod.default),
-		"is-dirty": () => import("./is-dirty-DYeJYhBz.mjs").then((mod) => mod.default),
-		"has-remote-changes": () => import("./has-remote-changes-C684Redh.mjs").then((mod) => mod.default),
-		dirty: () => import("./dirty-DNYoM6Bp.mjs").then((mod) => mod.default),
-		"current-task": () => import("./current-task-MpBFGttd.mjs").then((mod) => mod.default),
-		"cancel-task": () => import("./cancel-task-C5CU1pxU.mjs").then((mod) => mod.default),
-		wait: () => import("./wait-DoMDH226.mjs").then((mod) => mod.default),
-		import: () => import("./import-Rmmttboo.mjs").then((mod) => mod.default),
-		export: () => import("./export-BjfoZRDJ.mjs").then((mod) => mod.default),
-		stash: () => import("./stash-D0S4JmAz.mjs").then((mod) => mod.default),
-		branches: () => import("./branches-DchlyU0i.mjs").then((mod) => mod.default),
-		"create-branch": () => import("./create-branch-CYo6jZth.mjs").then((mod) => mod.default),
-		"add-collection": () => import("./add-collection-B3Ty8SzB.mjs").then((mod) => mod.default),
-		"remove-collection": () => import("./remove-collection-BOnxYvhj.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { git_sync_default as default };

package/dist/transform-Bs0EWijQ.mjs

@@ -1,28 +0,0 @@
-import { t as defineCommandGroup } from "./group-DBM87IgC.mjs";
-//#region src/commands/transform/index.ts
-var transform_default = defineCommandGroup({
-	name: "transform",
-	description: "Manage Metabase transforms",
-	skills: [{
-		skill: "transform",
-		purpose: "body shape, run-with-wait, iterate"
-	}, {
-		skill: "mbql",
-		purpose: "MBQL source.query bodies"
-	}],
-	subCommands: {
-		list: () => import("./list-C5Zs8nrb.mjs").then((mod) => mod.default),
-		get: () => import("./get-ByBOq30r.mjs").then((mod) => mod.default),
-		dependencies: () => import("./dependencies-Bj3QrGIm.mjs").then((mod) => mod.default),
-		create: () => import("./create-DJmXXQoq.mjs").then((mod) => mod.default),
-		update: () => import("./update-BCS5FxKr.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-Ck0q4Dzp.mjs").then((mod) => mod.default),
-		"delete-table": () => import("./delete-table-DuyhGrvA.mjs").then((mod) => mod.default),
-		run: () => import("./run-C3DkS6NP.mjs").then((mod) => mod.default),
-		cancel: () => import("./cancel-BMQa5R1Z.mjs").then((mod) => mod.default),
-		"get-run": () => import("./get-run-Cnux9ln0.mjs").then((mod) => mod.default),
-		runs: () => import("./runs-CUNWiidL.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_default as default };

package/dist/transform-job-BcLChRup.mjs

@@ -1,22 +0,0 @@
-import { t as defineCommandGroup } from "./group-DBM87IgC.mjs";
-//#region src/commands/transform-job/index.ts
-var transform_job_default = defineCommandGroup({
-	name: "transform-job",
-	description: "Manage Metabase transform jobs",
-	skills: [{
-		skill: "transform",
-		purpose: "tag-driven job schedules"
-	}],
-	subCommands: {
-		list: () => import("./list-BzVTHOoH.mjs").then((mod) => mod.default),
-		get: () => import("./get-DRvsATp-.mjs").then((mod) => mod.default),
-		create: () => import("./create-Beh-2uoN.mjs").then((mod) => mod.default),
-		update: () => import("./update-CmDTljK-.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-DFmX7jTp.mjs").then((mod) => mod.default),
-		run: () => import("./run-DdGJ544X.mjs").then((mod) => mod.default),
-		transforms: () => import("./transforms-oU4zizbO.mjs").then((mod) => mod.default),
-		"set-active": () => import("./set-active-BD8L1lPX.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_job_default as default };