Run a dbt Fusion project with Astronomer Cosmos. Use when running a dbt Fusion project with Astronomer Cosmos (Cosmos 1.11+, ExecutionMode.LOCAL on Snowflake/Databricks). Before implementing, verify dbt engine is Fusion (not Core), the warehouse is supported, and local execution is acceptable. Does

Cosmos + dbt Fusion: Implementation Checklist Execute steps in order. This skill covers Fusion specific constraints only. Version note : dbt Fusion support was introduced in Cosmos 1.11.0. Requires Cosmos ≥1.11. Reference : See [reference/cosmos config.md](reference/cosmos config.md) for ProfileConfig, operator args, and Airflow 3 compatibility details. Before starting , confirm: (1) dbt engine = Fusion (not Core → use cosmos dbt core ), (2) warehouse = Snowflake, Databricks, Bigquery and Redshift only. Fusion Specific Constraints Constraint Details No async AIRFLOW ASYNC not supported No virtualenv Fusion is a binary, not a Python package Warehouse support Snowflake, Databricks, Bigquery and Redshift support [while in preview](https://github.com/dbt labs/dbt fusion) 1. Confirm Cosmos Version CRITICAL : Cosmos 1.11.0 introduced dbt Fusion compatibility. Validate : pip show astronomer cosmos reports version ≥ 1.11.0 2. Install the dbt Fusion Binary (REQUIRED) dbt Fusion is NOT bundled with Cosmos or dbt Core. Install it into the Airflow runtime/image. Determine where to install the Fusion binary (Dockerfile / base image / runtime). Example Dockerfile Install Common Install Paths Environment Typical path Astro Runtime /home/astro/.local/bin/dbt System wide /usr/local/bin/dbt Validate : The dbt binary exists at the chosen path and dbt version succeeds. 3. Choose Parsing Strategy (RenderConfig) Parsing strategy is the same as dbt Core. Pick ONE: Load mode When to use Required inputs dbt manifest Large projects; fastest parsing ProjectConfig.manifest path dbt ls Complex selectors; need dbt native selection Fusion binary accessible to scheduler automatic Simple setups; let Cosmos pick (none) 4. Configure Warehouse Connection (ProfileConfig) Reference : See [reference/cosmos config.md](reference/cosmos config.md profileconfig warehouse connection) for full ProfileConfig options and examples. 5. Configure ExecutionConfig (LOCAL Only) CRITICAL : dbt Fusion with Cosmos requires ExecutionMode.LOCAL with dbt executable path pointing to the Fusion binary. 6. Configure Project (ProjectConfig) 7. Assemble DAG / TaskGroup Option A: DbtDag (Standalone) Option B: DbtTaskGroup (Inside Existing DAG) 8. Final Validation Before finalizing, verify: [ ] Cosmos version : ≥1.11.0 [ ] Fusion binary installed : Path exists and is executable [ ] Warehouse supported : Snowflake, Databricks, Bigquery or Redshift only [ ] Secrets handling : Airflow connections or env vars, NOT plaintext Troubleshooting If user reports dbt Core regressions after enabling Fusion: User Must Test [ ] The DAG parses in the Airflow UI (no import/parse time errors) [ ] A manual run succeeds against the target warehouse (at least one model) Reference Cosmos dbt Fusion docs: https://astronomer.github.io/astronomer cosmos/configuration/dbt fusion.html dbt Fusion install: https://docs.getdbt.com/docs/core/pip install dbt fusion Related Skills cosmos dbt core : For dbt Core projects (not Fusion) authoring dags : General DAG authoring patterns testing dags : Testing DAGs after creation

cosmos-dbt-fusion