-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add CLI flag to toggle warnings as errors #1243
Comments
This would also be great to have exposed in dbt Cloud, so jobs don't "fail" silently when there's nothing to do. This is sometimes the case after well-meant reorg efforts that change model locations and leave We recently moved a lot of models into a new/better folder structure. However, one of our dbt Cloud job that runs only a subset of the models via the It'd be great if the dbt Cloud job could be configured to either ignore warning or fail on warnings or otherwise had a way to configure failure levels. |
@clausherther yeah, i picture this being a CLI flag (just like I think we'll need to do some find/replace to make sure we catch all of the warnings, but I don't think this will be too gnarly a change to make |
Add flag for raising errors on warnings (#1243)
Feature
Feature description
We're running
dbt compile
as part of our CI process. Unfortunately when we getWARNING
s (i.e. schema test can't find the model), they are ignored. Users should be able to add a CLI flag to count warnings as errors (i.e.-werror
here)To get around this today, we run a bash script that contains:
Who will this benefit?
This would benefit anyone who wants to run checks as part of their dbt CI process. Helps ensure tests in production are being run.
The text was updated successfully, but these errors were encountered: