Skip to content

Commit

Permalink
Update reference-models-in-another-project.md
Browse files Browse the repository at this point in the history
  • Loading branch information
mirnawong1 authored Oct 6, 2023
1 parent 8b8d91f commit c7f009e
Showing 1 changed file with 2 additions and 6 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -7,17 +7,13 @@ keywords:
- project dependency, project dependencies, ref project, dbt mesh, multi-project, mesh, cross-project dependencies
---

You Check out the [docs](/docs/build/packages)
for more information!


Im dbt, you can manage dependencies across multiple dbt projects using:
I dbt, you can manage dependencies across multiple dbt projects using:

1. **Packages**: You can import [packages](/docs/build/packages) as a way to add another project to your dbt project, including other projects you've created. When you install a project as a package, you bring in its entire source code, making its macros and models available in your own project.

While this is useful for code reuse and sharing utility macros, it may not be the best approach for large-scale collaboration, especially in larger organizations.

4. **Project dependencies**: You can use [project dependencies](/docs/collaborate/govern/project-dependencies) as an exciting way to depend on another project using the metadata service in dbt Cloud. It instantly resolves references to public models defined in other projects. You don't need to execute or analyze these upstream models yourself. Instead, you treat them as an API that returns a dataset. The responsibility for maintaining the quality and stability of these public models lies with their respective maintainers.
2. **Project dependencies**: You can use [project dependencies](/docs/collaborate/govern/project-dependencies) as an exciting way to depend on another project using the metadata service in dbt Cloud. It instantly resolves references to public models defined in other projects. You don't need to execute or analyze these upstream models yourself. Instead, you treat them as an API that returns a dataset. The responsibility for maintaining the quality and stability of these public models lies with their respective maintainers.

This approach offers more flexibility and scalability for collaboration, making it easier to work with external projects while ensuring data quality and consistency.

Expand Down

0 comments on commit c7f009e

Please sign in to comment.