Open Jstein77 opened 2 months ago
Thanks for reporting this @Jstein77 🤩 See "reprex" below for a reproducible example.
Question for you: when using dbt v1.7, does it actually need to raise a friendly like the following?
Error: Could not run saved queries. The environment variable {env_var} is set to FALSE. Please set this the env var {env_var} to true in your dbt_project.yml, or include the --include-saved-query flag.
Or can it just behave the same way as v1.8 and show it as a NO-OP
?
dbt build --resource-type saved_query --no-include-saved-query
Is this a new bug in dbt-core?
Current Behavior
When on dbt 1.7 running
dbt build --resource-type saved_query
returns the following error when the env varDBT_INCLUDE_SAVED_QUERY
is not set.Instead of falling over, we should return an user friendly error with instructions on how to resolve the issue.
Expected Behavior
We should show a more user friendly error for example:
Steps To Reproduce
In 1.7 run
dbt build --resource-type saved_query
.Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response