Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

store_failures_as missing from project schema #147

Open
vonbraunbates opened this issue Jun 19, 2024 · 0 comments
Open

store_failures_as missing from project schema #147

vonbraunbates opened this issue Jun 19, 2024 · 0 comments

Comments

@vonbraunbates
Copy link

vonbraunbates commented Jun 19, 2024

The v1.7 and latest project schemas are missing valid values for store_failures_as. Since this was valid from v1.7 onwards, it's correct to be missing in v1.5 and v1.6.

This causes a validation error (e.g. using v8r):

Validating ./dbt_project.yml against schema from https://raw.githubusercontent.com/dbt-labs/dbt-jsonschema/main/schemas/latest/dbt_project-latest.json ...
✖ ./dbt_project.yml is invalid

./dbt_project.yml#/tests/+store_failures_as must be object
./dbt_project.yml#/tests/+store_failures_as must be null
./dbt_project.yml#/tests/+store_failures_as must match exactly one schema in oneOf

According to the docs:

The three supported values are:
ephemeral — nothing stored in the database (default)
table — test failures stored as a database table
view — test failures stored as a database view
You can configure it in all the same places as store_failures, including singular tests (.sql files), generic tests (.yml files), and dbt_project.yml.

Are there files for validating singular tests that I should also check for this bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant