From c3a136d2aaeed8e337982137bdfd3522b61a28f3 Mon Sep 17 00:00:00 2001 From: Jeremy Cohen Date: Tue, 20 Jun 2023 15:55:50 +0200 Subject: [PATCH] This might fix the links --- website/docs/docs/collaborate/govern/project-dependencies.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/collaborate/govern/project-dependencies.md b/website/docs/docs/collaborate/govern/project-dependencies.md index f75982aeb6d..1b0c5dc266d 100644 --- a/website/docs/docs/collaborate/govern/project-dependencies.md +++ b/website/docs/docs/collaborate/govern/project-dependencies.md @@ -9,7 +9,7 @@ description: "Reference public models across dbt projects" Cross-project `ref` This is a feature of dbt Cloud Enterprise. ::: -dbt Core v1.6 introduces a notion of `dependencies` between dbt projects. You're likely already familiar with installing other projects as [packages](packages), whereby you pull down another project's source code and treat it as your own. +dbt Core v1.6 introduces a notion of `dependencies` between dbt projects. You're likely already familiar with installing other projects as [packages](/docs/build/packages), whereby you pull down another project's source code and treat it as your own. There is a new kind of `project` dependency. Both dependencies can be defined in `dependencies.yml`: ```yml @@ -25,6 +25,6 @@ The first is familiar: I want to use macros from the `dbt_utils` package, and so The second is new. Unlike installing a package, the models in the `jaffle_finance` project will not be pulled down as source code, or selected to run during `dbt run`. Instead, dbt Cloud will provide `dbt-core` with expect stateful input that enables it to resolve references to public models in the `jaffle_finance` project—and _only_ the public models. -Models referenced from a `project`-type dependency must use [two-argument `ref`](ref#two-argument-variant), including the project name. Only public models can be accessed in this way. +Models referenced from a `project`-type dependency must use [two-argument `ref`](/reference/dbt-jinja-functions/ref#two-argument-variant), including the project name. Only public models can be accessed in this way. It's equally possible to install the `jaffle_finance` project as a `package` dependency. This will pull down its full source code., and require dbt to parse all its contents. dbt will expect you to configure and run those models as your own. This can be a useful pattern to achieve certain types of unified deployments in production. In development, it can add significant complexity and latency.