Skip to content

docs(dbt): fluid apply runs a build whatever its trigger, finds the dbt that has its adapter, and pins the container (forge-cli #1009) - #269

Merged
fas89 merged 2 commits into
mainfrom
claude/docs-dbt-wave16
Nov 19, 2026
Merged

fas89 merged 2 commits into
mainfrom
claude/docs-dbt-wave16

Conversation

@fas89

@fas89 fas89 commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

Documents forge-cli #1009, on main (caf4306d) after the 0.33.0 cut and in no release: fluid apply runs a dbt or Python build whatever its trigger type, finds the dbt that has the build's adapter by dbt's plugin name, and pins the dbt container fallback.

  • cli/generate.md: the paragraph about the container fallback now says what it did up to 0.33.0, and a new section, "Which dbt fluid apply runs", covers which dbt a build gets ($DBT_EXECUTABLE, the local dbt and its plugin name, Fusion), the container (the image pinned by digest, the packages pinned exactly and installed from wheels only, the isolated pip, the docker run command, the table of pinned adapters), the three variables with the refusals of a tag, a range and an adapter with no pin, and the AWS adapters (what is not passed into the container and the two refusals before docker starts).
  • advanced/environment-variables.md: the DBT_DOCKER_IMAGE, DBT_BOOTSTRAP_IMAGE and DBT_ADAPTER_PACKAGE rows.
  • advanced/airflow.md: one bullet in "What the DAG does": the trigger types that fluid apply runs once, with the output of 0.33.0 and of main for a schedule_and_dataset build.
  • upgrading.md: three bullets under "Not in a release yet".

Related CLI PRs

Areas Updated

  • Getting Started
  • CLI Reference
  • Provider Docs
  • Walkthroughs / Examples
  • Contributing / Community Docs
  • Other: advanced guides, upgrading

Decisions

  • The markers read *On forge-cli main, not yet in a release ([forge-cli #1009](...)).*: the pull request merged after the 0.33.0 cut. The pin stays at 0.32.0.
  • No new page: the container fallback was described in one paragraph of cli/generate.md and three rows of the environment variables page, so the new section sits beside that paragraph.
  • The outputs are real, without Docker, a container or an AWS call: forge-cli's dbt runner (the code fluid apply calls for a dbt build) with stand-ins for the local dbt's --version output and for docker, run on 0.33.0's code and on main for the trigger blocks, and on main for the container command and the refusals. The pins of the table are read from the code. Whether the pinned packages resolve on PyPI is the pull request's own record (a comment in the code); it was not run here.
  • $DBT_EXECUTABLE is used as it is, whatever adapter it has, so the page says so. The reviewer found that an earlier draft put it first in an order whose every step checks the adapter.
  • An adapter with no pin of its own (glue) runs in a container with DBT_ADAPTER_PACKAGE or with DBT_DOCKER_IMAGE, and the AWS credential checks come before the missing-pin refusal, so a reader without keys meets the credentials message first. The page and the bullet say so.

Checklist

  • python scripts/check_cli_docs.py (with forge-cli's live CHANGELOG.md), check_providers.py and gen_contract_reference.py --check pass
  • Site build, built-link check, offline link check and the linked anchors pass locally

Notes

  • A reviewer checked 78 sentences against the code, with 62 runs. Its six findings are fixed: the $DBT_EXECUTABLE order, dbt Fusion and the plugin match, the glue container (twice), the Redshift password case in the upgrading bullet, the DAG that does not decide when for event and timetable builds, and a message that names no field.
  • The code of #1009 on main equals the code the text was written and reviewed against (the pull request's head 6038b436) for every file but the changelog.
  • Docs main (docs(spark): a run starts only on the job config fluid apply compiled (forge-cli #1014) #268) is merged in.

…bt that has its adapter, and pins the container (forge-cli #1009)

Which dbt apply runs, the pinned container and its refusals, the three variables, the trigger types, and the upgrade bullets.
@fas89
fas89 merged commit 03c8f28 into main Nov 19, 2026
9 checks passed

This branch was previously deployed

1 inactive deployment
github-pages — f26b7e70 Deployed Nov 19, 2026 by fas89 via deploy #421
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant