-
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
support dbt packages that are not located at the root directory of a repo #275
Comments
@cmcarthur take a look--this might be relevant to the stuff you're working on right now. |
thanks @jthandy . there will indeed be an option to point to a local directory in a near future release |
this is doable today with local packages - closing this. |
I understand the specific use case mentioned in the issue is handled by the Would you consider still adding the feature of supporting sub directories? In |
@dmateusp I'm open to this! What do you have in mind? Given that |
@jtcohen6 I think the sparse checkout could be a good solution! I looked into how pip supports it, and it seems that they clone the whole repo https:/pypa/pip/blob/0dd3a2b84997e6d0cebcb7cf3e090e03bc2eedd9/src/pip/_internal/vcs/git.py#L358 |
Should be ready for review: #3267 |
…-pattern Handle schema pattern on BQ
via dbt slack:
question on dependency management. we initially have 2 services that we want to ‘own’ the initial model (transform) in our DW DB. specifically, we want them to run automated tests (in circleci) so that developers are prevented from making breaking changes to the source OLTP schema.
[2:54]
i believe ergonomically that means our
service-a
andservice-b
github repos have a./dbt
subfolder with some basic models (edited)[2:55]
which the service can run/test as part of the normal release for the service (edited)
[2:55]
and then a shared
bizint-models
repo that consumes those base models for more complex analyses[2:56]
however, it doesn’t look like the existing dependency management in dbt supports pulling from a small subdirectory in a (fairly large) service repo
The text was updated successfully, but these errors were encountered: