The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

I have a dbt cli resource which is configured to use the prod target. (the default one in the dbt config would be dev) but this is overwritten in dagsters resource to use PROD. For the materialization of the dbt run command - this works fine. However, dbt test somehow is falling back to the default configuration.

And this happens even tough I see: `dbt --no-use-color --log-format json test --project-dir /dbt_dir --profiles-dir /dbt_config_dir --target prod` in the logs.

Even in the logs It tells me that the that `prod` is used.

However, in the materialized `target/manifest` json files I see that instead the `dev` target was used

I can confirm that dagster is passing the target correctly.

however, somehow a subsequent step in the pipeline seems to ignore the target and use the default (and regenerate the manifest json)