@kapa.ai I recently upgraded to 0.23.0 (OSS/CLI version) and added the elementary_materialization macro to my dbt project. I am getting warnings now when I run dbt commands about setting package materialization override, which is no longer recommended in the instructions and I removed that flag when I added the macro. Should I still be setting package override to false as the warning says?

[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO - IMPORTANT - Starting from dbt 1.8, users must explicitly allow packages to override materializations.
[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO - Elementary requires this ability to support collection of samples and failed row count for dbt tests.
[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO - Please add the following flag to dbt_project.yml to allow it:
[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO - flags:
[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO -   require_explicit_package_overrides_for_builtin_materializations: false
[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO - Notes -
[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO - * This is a temporary measure that will result in a deprecation warning, please ignore it for now. Elementary is working with the dbt-core team on a more permanent solution.
[2026-04-23, 15:37:58 EDT] {process_utils.py:194} INFO - * This message can be muted by setting the 'mute_ensure_materialization_override' var to true.

Based on the knowledge sources, this is a known situation that has been addressed in newer versions of Elementary. What's Happening The warning message you're seeing is Elementary's internal check that fires when it detects dbt 1.8+. Importantly, this message is printed by Elementary itself (not dbt), and it fires unconditionally as a safeguard — even when your custom materialization macro is already in place and working correctly. [Slack thread] Should You Re-add the Flag? No. The newer recommended approach (which you've already followed) is: 1. Add the

elementary_materialization.sql

macro to your project's

macros/

folder. 2. Remove the

require_explicit_package_overrides_for_builtin_materializations: false

flag — which you've already done correctly. The macro in your project takes precedence over the package's materialization due to dbt's macro resolution order, and this is the explicit override mechanism that avoids the dbt deprecation warning. [Install package] Why You're Still Seeing the Message Elementary's internal warning message is printed before it can verify whether your custom macro override is active. It's a proactive reminder, not an indication that the override isn't working. The message itself notes it can be muted by setting:

vars:
  mute_ensure_materialization_override: true

However, be aware that users have reported this var doesn't always fully suppress the message in all environments — it's a known open issue. [Slack thread] Summary • ✅ Keep your

elementary_materialization.sql

macro in place • ✅ Keep the flag removed (do not re-add

require_explicit_package_overrides_for_builtin_materializations: false

) • ✅ Optionally set

mute_ensure_materialization_override: true

to suppress the message • The warning does not indicate a malfunction — your setup is correct 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.