[env_vars] [false positives] environment-aware logic for sources should not cause sources to always be marked as modified

[graciegoheen]

To support this pattern with sources (and probably other "yaml-only" resource types), I believe we'd need to also do the work of treating database + schema + identifier/alias as configs, such that we can save their unrendered values when configs are calculated. In theory, that's happening here, but it doesn't work as I'd expect for the one actual source config we do support today, enabled.

Original issue for this:

• Store the unresolved form of source database representations #2744

Originally posted by @jtcohen6 in #9563 (comment)

I want to point to a different locations for my sources depending on the environment I am in (different database for prod vs. dev). To do so, I configure my sources as follows:

sources:
  - name: jaffle_shop
    database: "{{ env_var('DBT_DATABASE'}}"
    tables:
      - name: customers

But, this counts as a modified change everytime I do --select state:modified comparing two different environments.

Instead, I tried putting this logic in dbt_project.yml:

sources:
  project:
    +database: ...

and that did not work, as it seems the only configuration that is available to sources in the dbt_project.yml is enabled - docs here.

Acceptance Criteria

• I want to use env_vars in my configuration, and the resource should not always be marked as modified

We should open a separate ticket to handle env_vars for other resources

Relevant to #4304

[ashleemtib]

Hi there, just curious if this is slotted for work any time soon?

[graciegoheen]

Hi @ashleemtib, yes! Currently, we're planning to tackle this work for 1.9