Improve dbt environment management
Discussed in #3156 (comment 810106268).
switching environments - Similar to how in the squared repo we use the environments feature to make it easy to switch between dbt environments. This might already be supported but just needs documentation on how best to use it. Or theres a way to make it even smoother.
In addition to just simply making it easier to swap between "virtual environments" (isolated schema, etc.) we could also help with the cloning process that most teams are trying to run in CI. Its a common struggle for teams to figure out the best way to test their dbt models prior to releasing to prod, maybe they want to release using blue/green deployments too. This is a solid amount of work to figure out for a team. Cloning data, running tests on a subset of models to save on cost, blue/green deploys.
The way I did this in the past was using macros. We could have a suite of macros that help do some of these things. It might be challenging to do this cross warehouse platform (i.e. its very easy to zero copy clone in Snowflake but maybe not everywhere else).