You’re running into two different kinds of warnings in the docs: 1. Deprecated

current_timestamp

macro / dbt-utils warning Elementary relies on

dbt_utils.current_timestamp

, which is deprecated and prints a warning. There is **no supported way to silence this via macros or config in dbt today**; Elementary’s team confirmed “we’ll just have to live with the warnings” until dbt-core provides an equivalent and Elementary can switch to it.[\[current_timestamp warning\]](https://slack.com/archives/C02CTC89LAX/p1663959791369669) So for this specific warning, you cannot turn it off with a macro or var. 2. Materialization override warnings (

elementary

overriding `table`/`test`) dbt 1.7/1.8+ now warns when a package overrides built‑in materializations. Elementary’s current guidance is: - For dbt < 1.8: you can ignore the warning; Elementary works normally. - For dbt ≥ 1.8: you can add this to

dbt_project.yml

to ensure Elementary still works as expected:

yaml      flags:        require_explicit_package_overrides_for_builtin_materializations: false

This does not remove the warning, it only guarantees the behavior keeps working.[\[override warning\]](https://slack.com/archives/C02CTC89LAX/p1715016357916139) Elementary also documents

mute_ensure_materialization_override: true

, but users report that this currently does not mute the dbt warning and the docs note that this is an open issue they’re working with dbt-core to resolve.[\[mute var issue\]](https://slack.com/archives/C08HW57FGN9/p1742322227557429;https://slack.com/archives/C02CTC89LAX/p1727244860265519) 3. Using vars/macros to control Elementary behavior - Some warnings from Elementary itself (e.g., auto‑upload hooks) can be turned off with vars in

dbt_project.yml

, e.g.:

yaml      vars:        disable_dbt_artifacts_autoupload: true

which also stops the associated hook behavior.[\[artifacts var\]](https://slack.com/archives/C02CTC89LAX/p1672763854939849) - These vars must be set under the top‑level

vars:

key in

dbt_project.yml

, not nested under

elementary:

.[\[vars placement\]](https://slack.com/archives/C02CTC89LAX/p1684237913992769) - You cannot use custom macros (like

{{ dummy_true() }}

) inside

dbt_project.yml

to dynamically set

enabled

or vars; dbt doesn’t allow that. You can only use `var()`/`env_var()` (with some limitations) or

--vars

on the CLI.[\[dummy_true limitation\]](https://slack.com/archives/C02CTC89LAX/p1679922455962869) Given the knowledge sources: - If your warning is the dbt-utils

current_timestamp

deprecation – you **cannot silence it with macros or vars right now**; you have to ignore it until Elementary/dbt-utils/dbt-core change their implementation. - If your warning is the materialization override warning – you can add the

flags:

config above to keep things working, but the warning will still appear until dbt and Elementary ship a permanent mechanism. - Vars like

mute_ensure_materialization_override

exist but do not yet reliably remove the dbt warning, and Elementary explicitly calls that out as an open issue. If you share the exact warning text, I can point to the precise config (or confirm that, per the docs, it simply can’t be muted yet).