From 89f3e7ca4773bf6bc2686b2336bd6abf8014337c Mon Sep 17 00:00:00 2001 From: Lightdash Bot <131011178+lightdash-bot@users.noreply.github.com> Date: Sun, 1 Nov 2026 20:52:45 +0000 Subject: [PATCH 1/2] Document the Tags field for dbt Cloud connections --- integrations/connect-project.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/integrations/connect-project.mdx b/integrations/connect-project.mdx index cfeac947..411d2a39 100644 --- a/integrations/connect-project.mdx +++ b/integrations/connect-project.mdx @@ -1772,6 +1772,16 @@ The dbt Cloud metadata API host for your region. Must use `https://`. Match it t - EU multi-tenant: `https://metadata.eu1.dbt.com` - Cell-based (URL like `abc123.us1.dbt.com`): `https://.metadata.us1.dbt.com` +##### Tags + +Only models that carry **all** the tags you list here are synced. Lightdash passes the tags as a filter to the dbt Cloud Discovery API, together with `lastRunStatus: success`, so a model is synced only if it has every listed tag in the connected environment's last successful run. The [dbt selector](/integrations/dbt/projects#dbt-selector) setting doesn't apply to dbt Cloud connections. + +Limiting the synced models also reduces the number of warehouse tables Lightdash looks up on each refresh. + + + If no model in the last successful run carries all the listed tags, the sync fails with "No models found". After you add a tag to a model in dbt, a job must run in that environment before you refresh Lightdash — Lightdash only sees tags from the environment's last successful run. + + *** ### CLI From 050f7c7af205b76717be293f34aa4e56ccc4581f Mon Sep 17 00:00:00 2001 From: Lightdash Bot <131011178+lightdash-bot@users.noreply.github.com> Date: Sun, 1 Nov 2026 22:38:11 +0000 Subject: [PATCH 2/2] Document the CLI's in-place preview credential refresh --- workflow/preview-projects.mdx | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/workflow/preview-projects.mdx b/workflow/preview-projects.mdx index 654283c9..62a67458 100644 --- a/workflow/preview-projects.mdx +++ b/workflow/preview-projects.mdx @@ -106,6 +106,8 @@ It can also fail if your warehouse identity doesn't have permission to run queri To use the upstream project's saved warehouse connection instead of your own credentials, run `lightdash preview --no-warehouse-credentials`. +If queries fail with a session-expired error (for example `Your Redshift IAM AWS session has expired`), see [Redshift with `method: iam`](#redshift-with-method-iam) to refresh the credentials on your existing preview instead of recreating it. + ### Switch between previews The CLI keeps one active preview: the last one you started. `lightdash deploy`, `lightdash upload`, and `lightdash download` ask whether to use it or your production project, and use the preview in non-interactive mode. Starting another preview doesn't delete the previous one. It stays on the server until you run `lightdash stop-preview --name` with its name, or it [expires](#preview-expiration). @@ -127,7 +129,18 @@ aws sso login --profile my-redshift-profile lightdash preview ``` -Because SSO and role credentials are short-lived, the CLI prints a warning showing the expiry when it forwards temporary credentials. Queries in the preview project will stop working once the session expires. Re-run `aws sso login` and `lightdash preview` to refresh them. +Because SSO and role credentials are short-lived, the CLI prints a warning showing the expiry when it forwards temporary credentials. Queries in the preview project will stop working once the session expires. + +On CLI 2.186.1 or newer, you don't need to stop and recreate the preview to refresh them. Update the CLI (`npm i -g @lightdash/cli@latest` — CLI versions compare numerically per segment, so 2.449 is newer than 2.57), sign in again, then re-run `start-preview` with the same `--name`: + +```bash +aws sso login --profile my-redshift-profile +lightdash start-preview --name "my-preview" +``` + +This pushes the newly resolved credentials into the existing preview instead of creating a new one, so content you've built in the preview — dashboards, data apps — stays in place. The command prints `Warehouse credentials refreshed` on success. If it prints `Keeping the warehouse credentials already stored on the preview` instead, the refresh was skipped — most often because the prompt to let Lightdash store your warehouse credentials was declined. Pass `-y`/`--assume-yes` to accept that prompt automatically. The refresh is also skipped when the preview was started with `--no-warehouse-credentials` or an organization warehouse credential, since neither reads credentials from your local `profiles.yml`. The refreshed connection keeps any SSH tunnel settings inherited from the upstream project. + +The same refresh applies to any other warehouse credentials the CLI resolves locally and that expire, such as a Snowflake SSO session. This applies to ephemeral preview projects created from your local dbt profile. For a durable, persistent project connection to Redshift with IAM, use a role the Lightdash backend assumes (`assumeRoleArn`). See [Connect Redshift](/integrations/connect-project#redshift).