Lift + shift for cross-db macros

[jtcohen6]

Follow-up to:

• Initialize lift + shift for cross-db macros dbt-core#5265
• Initialize lift + shift for cross-db macros dbt-utils#594
• Initialize lift + shift for cross-db macros dbt-spark#359

[jtcohen6]

Functional tests are running, which is actually amazing. The other tests are running into a dbt-core error while parsing profiles.yml, which I've just opened as dbt-labs/dbt-core#5268

[jtcohen6]

The idea would be:

• A new minor release, requiring dbt-core v1.2.0, with backwards compatibility for folks calling these macros directly — spark_utils.dateadd. I don't think that's many people, but still!
• A subsequent minor release that removes all backwards compatibility

[dbeatty10]

You are amazing.

Love the creation of the macros/dbt_utils/cross_db_utils/deprecated folder. Separates things nicely.

[dbeatty10]

This is helpful!

[dbeatty10]

Last Week I Learned (LWIL):

• By default pytest-dotenv will not override any variables already defined in the process' environment

Example

Let's say I have an environment variable defined locally:
DBT_DATABASE_HOST=localhost

And test.env contains:
DBT_DATABASE_HOST=somethingelse

By default, pytest-dotenv will keep the former and ignore the latter. Scroll down to see how to configure the opposite behavior.

Override default behavior

So it depending on how we want pytest + pytest-dotenv to behave, we either will want to include the following (or not!):

env_override_existing_values = 1

[jtcohen6]

A great LWIL!

This makes sense to me, insofar as I might have a test.env, but then also want to do:

export DBT_DATABASE_HOST=localhost
python3 -m pytest ...

I would indeed expect the env var I've just supplied to override the one in test.env