Closed peterallenwebb closed 1 week ago
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.
Short description
A couple of months ago, we added InvocationContext, a cross-thread context manager supporting isolation between dbt invocations. Now we want to support extensions and modifications of its runtime behavior without requiring changes in dbt-common. This will mean designing and implementing a general mechanism for registering and using context objects. Uses cases include:
The key will be to provide a way to register and manage the lifetimes of these objects with the InvocationContext, while allowing them to be defined and implemented in the libraries that depend on dbt-common.
Acceptance criteria
TBD
Suggested Tests
TBD
Impact to Other Teams
None
Will backports be required?
No