Jeremy Cohen

> TODO: Consider only migrating the new logger? Depends on timing of RPC replacement. We think we have a path to migrate from the legacy to new logger, and it's...

Resolved by https://github.com/dbt-labs/dbt-core/pull/6088

Conceptually, good by me! This section of the codebase is tricky (along with all config initialization). We'll definitely want some tests for this behavior as well. I marked `ready_for_review`, and...

@dbeatty10 I just left a big comment over in https://github.com/dbt-labs/dbt-core/pull/5717#issuecomment-1249218025! I forgot the main PR was over here. What's the difference between these two? After checking through the codebases, I...

@dbeatty10 Huzzah! I am thrilled to move forward with whichever of these PRs you wish :) I think the move now is to close one, and request review on the...

@gshank I'm assuming it's safe to close this one — please reopen if I'm mistaken!

@avnav88 Thanks for opening! I don't know if we've ever tested running `dbt init` from one of our Docker containers. I wouldn't be surprised if this is an issue that's...

Legit! Thanks for opening @NiallRees. I don't think there would be any security concerns related to this, as long as we keep it tightly locked down to _just_ the environment...

> FYI: My ongoing plan for any future macros is https://github.com/dbt-labs/dbt-utils/discussions/487#discussioncomment-3185750 - in short, if someone need a new cross-db macro, they add it to their own package until the...

@charlespicowski Thanks for opening! Manifest data has been getting bigger and bigger. This reflects both: - The addition of new configuration options within dbt, while preserving backwards compatibility for metadata...