From 0eb8fdd908757099fa5f4441151cd913d77c942c Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 18 May 2026 14:23:53 +0000 Subject: [PATCH] docs: document --combine-manifest flag on lightdash deploy --- references/lightdash-cli.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/references/lightdash-cli.mdx b/references/lightdash-cli.mdx index 89f7058e..f6bb4379 100644 --- a/references/lightdash-cli.mdx +++ b/references/lightdash-cli.mdx @@ -443,6 +443,8 @@ All standard [dbt options](#dbt-options) work with `lightdash deploy`. - `--use-dbt-list [true|false]` - (default: true) - Use `dbt list` instead of `dbt compile` to generate dbt manifest.json +- `--combine-manifest ` + - Path to an additional dbt `manifest.json`. Models present in this file but missing from the deploy-generated manifest are merged in so the deploy reflects the full project even when dbt was only run on a subset of models. The deploy-generated manifest always wins on conflicts. - `--use-batched-deploy` - (default: false) - Deploy explores in batches instead of a single request. Useful for large projects that exceed payload size limits @@ -474,6 +476,12 @@ Deploy with custom batch settings for very large projects: lightdash deploy --use-batched-deploy --batch-size 100 --parallel-batches 3 ``` +Deploy a subset of models while keeping the rest of the project intact by merging in an existing manifest: + +```bash +lightdash deploy --select "tag:marketing" --combine-manifest ./prod-manifest.json +``` + ### `lightdash refresh`