-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loosely Couple CLI #4179
Comments
Realistically, this same approach should be applied to the cli, all environment variables, and reading files, probably in that order. |
I know we've discussed this previously: As part of splitting out / rewriting the CLI, we should also consider alternatives to
|
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 remove the stale label or comment on the issue, or 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; add a comment to notify the maintainers. |
Is there an existing feature request for this?
Describe the Feature
I would like to see the dbt cli loosely coupled from the rest of the core code base. This way the cli could be parsed into an object, and the rest of the code can access that object's fields. Today we have the cli parsing arguments and mutating global state without saving the original values, which makes it difficult to respect the inputs users have given us later in the flow.
Additionally, users have noticed how slow the CLI is to start up (e.g. - #4627), and separating out the CLI would allow us to more easily return quickly without loading unnecessary resources when we invoke dbt with invalid arguments or just ask for the version.
Describe alternatives you've considered
We could just keep adding global mutations of values ad-hoc every time we need them. It's just messy and keeps the cli unnecessary tightly coupled.
Who will this benefit?
dbt core devs and community contributors.
Are you interested in contributing this feature?
Yes
Anything else?
No response
The text was updated successfully, but these errors were encountered: