dbt full refresh global config does not work

[bmarcj]

Dagster version

1.8.7

What's the issue?

Documentation on dbt global configs is found here:

https://docs.getdbt.com/reference/global-configs/about-global-configs

This includes the fairly critical --full-refresh flag.

Dagster documentation:
https://docs.dagster.io/_apidocs/libraries/dagster-dbt#dagster_dbt.DbtCliResource.global_config_flags

Global flags are supposed to be supported by this setting.

Unfortunately, the dagster implementation places global flags at the start of the command e.g.

dbt --full-refresh build ...

This causes an error with the dbt command line (it expects this to be at the end of the invocation).

What did you expect to happen?

The flag should be in the correct place to work.

How to reproduce?

Run a dbt asset with the global config set to ["--full-refresh"]

Deployment type

None

Deployment details

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[clairelin135]

Thanks for reporting, I'm adding a PR to fix: #24615

[bmarcj]

Thanks @clairelin135. That's a fine fix for this issue. Are there plans to support full refresh for dbt out of the box, or is this feature integration something users are expected to handle themselves?