Skip to content

blog: Kestra now supports dbt Core v2.0 and the Fusion engine#4901

Open
elliotgunn wants to merge 3 commits into
mainfrom
blog/dbt-fusion-kestra
Open

blog: Kestra now supports dbt Core v2.0 and the Fusion engine#4901
elliotgunn wants to merge 3 commits into
mainfrom
blog/dbt-fusion-kestra

Conversation

@elliotgunn

@elliotgunn elliotgunn commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

⚠️ Do NOT merge this blog post until this PR is merged and released and the 2.0.0 dbt Docker images built by Plugins squad.

Summary

  • Adds blog post announcing Kestra's dbt plugin support for dbt Core v2.0 and the Fusion engine
  • Covers the new engine: FUSION property on DbtCLI, state-based selection (--select state:modified+), and zero breaking changes for existing users
  • Links to the Fivetran + dbt merger resource page and existing dbt Core orchestration guide

Before merging

  • Blog banner image (main.png) needs to be added to src/contents/blogs/dbt-fusion-kestra/ — post will not render correctly without it, design request here https://github.com/kestra-io/design/issues/70
  • Confirm engine: FUSION plugin syntax matches what ships in plugin-dbt#272

Announces plugin-dbt v2.0 support for the Fusion engine, including the
new engine property on DbtCLI, updated CLI flag handling, and
state-based selection patterns.
@aj-emerich

Copy link
Copy Markdown
Member

@elliotgunn, I think saying "zero breaking changes" isn't quite right. Assessing the PR surfaced the following:

Three previously valid CLI flags (--no-partial-parse,
--partial-parse, --models) now either silently misbehave or error under Fusion.

It would be good to minimally flag this in the post. CC: @fdelbrayelle

@fdelbrayelle fdelbrayelle added the kind/do-not-merge Don't merge label Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants