[X] I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
Given a model with environment-based dependencies:
select 1 as id
{% if target.name == "prod" %}
-- depends_on : {{ ref('data_change_model') }}
{% else %}
-- depends_on : {{ ref('column_added_model') }}
{% endif %}select 1 as id
{% if target.name == "prod" %}
-- depends_on : {{ ref('data_change_model') }}
{% else %}
-- depends_on : {{ ref('column_added_model') }}
{% endif %}
given a prod (deferred) and dev manifest, dbt does not pick this up as a modified node in state:modified because it does not consider the node's depends_on (most often this is proxied by the node body contents)
Expected Behavior
dbt picks up the modified model between prod & dev runs as the depends_on have changed
Is this a new bug in dbt-core?
Current Behavior
Given a model with environment-based dependencies:
given a prod (deferred) and dev manifest, dbt does not pick this up as a modified node in state:modified because it does not consider the node's
depends_on
(most often this is proxied by the node body contents)Expected Behavior
dbt picks up the modified model between prod & dev runs as the depends_on have changed
Steps To Reproduce
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
No response