Dan Cook
12/04/2024, 10:30 PMprofiles.yml file: snowflake_prod and snowflake_dev. The default target/profile is snowflake_dev, which points to the database/schema where we dbt run our models during development, and only when a model is ready for prime time do we check it into Github and use Airflow to dbt run -t snowflake_prod.
Historically we've also run dbt test against the snowflake_dev target, but our project's maturity is at the point where we want to switch our regular testing via dbt test -t snowflake_prod.
The actual tests against our snowflake_prod target execute fine (some log output below), but the browser-based output of edr report can't be coaxed into showing these results (screenshot); the browser-based report only shows valid test results if we ran dbt test against our snowflake_dev target.
I've tried to use variations on the --project-profile-target command line option for edr, but these haven't solved my problem.
(p.s. I'm using elementary OSS with Snowflake)Dan Cook
12/06/2024, 7:54 PMdbt run / dbt test.
Otherwise dbt run -s elementary doesn't write useful data into artifact tables like "elementary_test_results", and therefore edr report doesn't have anything to report on.
Is it the case that we can't segregate the artifacts to a Snowflake database different from where the tested models live?Dan Cook
12/06/2024, 7:54 PM