19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
g
geoHeil
12/15/2022, 3:29 PMI 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 prodEven in the logs It tells me that the that
prodHowever, in the materialized
target/manifestdevI 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)