Pichon Simon
04/15/2025, 9:11 AMkapa.ai
04/15/2025, 9:11 AMkapa.ai
04/15/2025, 9:12 AMdbt_project.yml file: yaml vars: disable_run_results: true disable_tests_results: true disable_dbt_artifacts_autoupload: true disable_dbt_invocation_autoupload: true This will disable the various hooks that Elementary uses to collect and upload metadata [FAQ documentation](https://docs.elementary-data.com/oss/general/faq). ### Option 2: Disable the entire Elementary package If you want to completely disable Elementary models and hooks, you can add this to your `dbt_project.yml`: yaml models: elementary: +schema: "elementary" +enabled: false # or use a conditional like "{{ target.name == 'prod' }}" This will disable all Elementary models, including the hooks [FAQ documentation](https://docs.elementary-data.com/oss/general/faq). ### Option 3: Selectively enable Elementary models If you still want to use some Elementary functionality but control when the models run: yaml models: elementary: +schema: elementary edr: +enabled: "{{ var('enable_elementary_models', false) }}" Then you can explicitly run Elementary models when needed: dbt run --select elementary --vars '{"enable_elementary_models": true}' While the knowledge sources don't specifically address dbt_project_evaluator or dbt_snowflake_monitoring, these approaches should help you control when Elementary's functionality runs. If these packages are running as part of Elementary's processes, disabling the hooks or the entire package should prevent them from executing. If you need more specific guidance about these particular packages, you might need to check their documentation or reach out to Elementary support directly.