From ba924fd58dd0f119a73616b4cb5c83c99deddc75 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Oct 2023 14:12:49 +0100 Subject: [PATCH 01/10] Update reference-models-in-another-project.md add info on project dependencies. Closes #4026 --- .../reference-models-in-another-project.md | 20 ++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md index 19f3f52da31..fc06d1dfa4f 100644 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ b/website/docs/faqs/Models/reference-models-in-another-project.md @@ -3,9 +3,23 @@ title: How can I reference models or macros in another project? description: "Use packages to add another project to your dbt project" sidebar_label: 'Reference models or macros in another project' id: reference-models-in-another-project - +keywords: + - project dependency, project dependencies, ref project, dbt mesh, multi-project, mesh, cross-project dependencies --- -You can use [packages](/docs/build/packages) to add another project to your dbt -project, including other projects you've created. Check out the [docs](/docs/build/packages) +You Check out the [docs](/docs/build/packages) for more information! + + +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. + +This approach offers more flexibility and scalability for collaboration, making it easier to work with external projects while ensuring data quality and consistency. + + + From 8b8d91f8ad2959f6fee68a9b519e1cc0b8e84b88 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Oct 2023 14:14:14 +0100 Subject: [PATCH 02/10] Update website/docs/faqs/Models/reference-models-in-another-project.md --- website/docs/faqs/Models/reference-models-in-another-project.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md index fc06d1dfa4f..17790152493 100644 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ b/website/docs/faqs/Models/reference-models-in-another-project.md @@ -11,7 +11,7 @@ You Check out the [docs](/docs/build/packages) for more information! -I dbt, you can manage dependencies across multiple dbt projects using: +Im 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. From c7f009e9eeddb7a18cc202969577f930db37e4c6 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Oct 2023 14:14:36 +0100 Subject: [PATCH 03/10] Update reference-models-in-another-project.md --- .../faqs/Models/reference-models-in-another-project.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md index 17790152493..619a38e336f 100644 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ b/website/docs/faqs/Models/reference-models-in-another-project.md @@ -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. From 993e718b160fbe1903e5dfedf80b9435a36ec94f Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Oct 2023 14:14:51 +0100 Subject: [PATCH 04/10] Update website/docs/faqs/Models/reference-models-in-another-project.md --- website/docs/faqs/Models/reference-models-in-another-project.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md index 619a38e336f..2c4ffba8374 100644 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ b/website/docs/faqs/Models/reference-models-in-another-project.md @@ -7,7 +7,7 @@ keywords: - project dependency, project dependencies, ref project, dbt mesh, multi-project, mesh, cross-project dependencies --- -I dbt, you can manage dependencies across multiple dbt projects using: +In 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. From 58376bad5e911e5944b705c4a02bd48f708d0252 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Oct 2023 14:15:33 +0100 Subject: [PATCH 05/10] Update website/docs/faqs/Models/reference-models-in-another-project.md --- website/docs/faqs/Models/reference-models-in-another-project.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md index 2c4ffba8374..ef9c0ba4dfa 100644 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ b/website/docs/faqs/Models/reference-models-in-another-project.md @@ -11,7 +11,7 @@ In 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. +While this is useful for reusing code and sharing utility macros, it may not be the best approach for large-scale collaboration, especially in larger organizations. 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. From acae90d1a913dbc817358c6664cad332345745e2 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Oct 2023 14:16:00 +0100 Subject: [PATCH 06/10] Update website/docs/faqs/Models/reference-models-in-another-project.md --- website/docs/faqs/Models/reference-models-in-another-project.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md index ef9c0ba4dfa..fe83fdbdbe8 100644 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ b/website/docs/faqs/Models/reference-models-in-another-project.md @@ -9,7 +9,7 @@ keywords: In 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. +1. **Packages**: You can install [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 reusing code and sharing utility macros, it may not be the best approach for large-scale collaboration, especially in larger organizations. From 03cc1fb963ba036112beaec91ded0ab692e97b4a Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 6 Oct 2023 14:16:32 +0100 Subject: [PATCH 07/10] Update website/docs/faqs/Models/reference-models-in-another-project.md --- website/docs/faqs/Models/reference-models-in-another-project.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md index fe83fdbdbe8..f305bc2ba0f 100644 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ b/website/docs/faqs/Models/reference-models-in-another-project.md @@ -11,7 +11,7 @@ In dbt, you can manage dependencies across multiple dbt projects using: 1. **Packages**: You can install [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 reusing code and sharing utility macros, it may not be the best approach for large-scale collaboration, especially in larger organizations. +While this is useful for reusing code and sharing macros, it may not be the best approach for large-scale collaboration, especially in larger organizations. 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. From 7017d0c103b06a06dffec6e1203c10346e9ac4d5 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 9 Oct 2023 11:00:58 +0100 Subject: [PATCH 08/10] Delete website/docs/faqs/Models/reference-models-in-another-project.md --- .../reference-models-in-another-project.md | 21 ------------------- 1 file changed, 21 deletions(-) delete mode 100644 website/docs/faqs/Models/reference-models-in-another-project.md diff --git a/website/docs/faqs/Models/reference-models-in-another-project.md b/website/docs/faqs/Models/reference-models-in-another-project.md deleted file mode 100644 index f305bc2ba0f..00000000000 --- a/website/docs/faqs/Models/reference-models-in-another-project.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: How can I reference models or macros in another project? -description: "Use packages to add another project to your dbt project" -sidebar_label: 'Reference models or macros in another project' -id: reference-models-in-another-project -keywords: - - project dependency, project dependencies, ref project, dbt mesh, multi-project, mesh, cross-project dependencies ---- - -In dbt, you can manage dependencies across multiple dbt projects using: - -1. **Packages**: You can install [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 reusing code and sharing macros, it may not be the best approach for large-scale collaboration, especially in larger organizations. - -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. - - - From 158b168a39f86984239a57a1efdd2e4ac6ff30f0 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 9 Oct 2023 11:02:40 +0100 Subject: [PATCH 09/10] Update vercel.json add redirect for faq --- website/vercel.json | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/vercel.json b/website/vercel.json index c5fb0638fba..4813fb423c4 100644 --- a/website/vercel.json +++ b/website/vercel.json @@ -2,6 +2,12 @@ "cleanUrls": true, "trailingSlash": false, "redirects": [ + + { + "source": "/faqs/Models/reference-models-in-another-project", + "destination": "/docs/collaborate/govern/project-dependencies", + "permanent": true + }, { "source": "/docs/deploy/job-triggers", "destination": "/docs/deploy/deploy-jobs", From 3ceca4d741a9067c28cfb140adbe139d3054c40b Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 10 Oct 2023 10:47:34 +0100 Subject: [PATCH 10/10] Update vercel.json --- website/vercel.json | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/vercel.json b/website/vercel.json index 4813fb423c4..072062ec939 100644 --- a/website/vercel.json +++ b/website/vercel.json @@ -2,7 +2,11 @@ "cleanUrls": true, "trailingSlash": false, "redirects": [ - + { + "source": "/faqs/models/reference-models-in-another-project", + "destination": "/docs/collaborate/govern/project-dependencies", + "permanent": true + }, { "source": "/faqs/Models/reference-models-in-another-project", "destination": "/docs/collaborate/govern/project-dependencies",