-
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
[Feature] CLI Parameter for packages-install-path
#9932
Comments
Thanks for opening this @stevenayers ! Can you share more about the specific use cases where combining a CLI flag with an environment variable is necessary or beneficial versus just merely including the |
Hi @dbeatty10, sure no problem! Let me break this down a bit. Hardcoding
|
Yesterday @jtcohen6 and myself had a chance to discuss the proposed new CLI flag + environment variable. SummaryThe general caseWe've approached where flags can be set differently depending on use-case:
So generally, we don't let these be set in both places, and it would take a really compelling case for us to do so. This specific caseIn this case, it sounds like the main barrier is that setting environment variables is difficult within Databricks DBT Workflows. If this is the primary barrier, then we'd prefer not to add a new feature to dbt in order to work around it. So we're closing this and the associated PR in #9933 as not planned. But if anyone can provide additional examples why should consider supporting a new |
Is this your first time submitting a feature request?
Describe the feature
Add a CLI parameter for the
packages-install-path
, similar to howtarget-path
has one.In the docs, under target-path, it says:
Describe alternatives you've considered
Using the env var
DBT_PACKAGES_INSTALL_PATH
.The issue here is that some orchestration tools, such as Databricks DBT Workflows make setting environment variables very difficult. By adding this cli parameter, we maintain consistency across global configs.
Who will this benefit?
People using orchestration tools with awkward limitations.
Are you interested in contributing this feature?
Yes, the PR is #9933
The text was updated successfully, but these errors were encountered: