Hi Team! We released a hotfix for a problem in disabling elementary hooks using Jinja expressions. These disablement methods are now tested and validated:

vars:
  disable_run_results: "{{ target.name != 'prod' }}"
  disable_dbt_artifacts_autoupload: "{{ (target.name != 'prod') | as_bool }}"
  disable_dbt_invocation_autoupload: "{{ target.name != 'prod' }}"
  ...

The new version of the dbt package is 0.6.4, change the

packages.yml

and run

dbt deps

. Thanks @Josh Elston-Green for reporting and helping us figure this out. _Please note_: If you were using any of the disablement vars (

disable_*

) with a Jinja expression (most notably

target.name != prod

) rather than

true

or

false

, up until now, it would've always been disabled regardless of the expression. If you're interested, technicals details as to what was the problem in the thread 🧵.

Hi Elon! Can I confirm, if I add these three lines to our project's

dbt_project.yml

, then elementary will not run anything except on target prod, correct? Asking as we are looking at implementing this, but I don't want to make our analysts run elementary locally during development (both due to the extra processing time and the initial

--select elementary

I believe they would have to run)

Hi @Franny (Procore), if you'd like to run Elementary in production only, you can do the following in your `dbt_project.yml`:

models:
  elementary:
    +enabled: "{{ target.name == 'prod' }}"

Let me know if you have any further questions, would love to help.

Oo, lovely, thanks!