Skip to content
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

Package dependencies may be included in either packages.yml or dependencies.yml #6029

Merged
merged 4 commits into from
Sep 26, 2024
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/snippets/_packages_or_dependencies.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Starting from dbt v1.6, we added a new configuration file called `dependencies.y

If your dbt project doesn't require the use of Jinja within the package specifications, you can simply rename your existing `packages.yml` to `dependencies.yml`. However, something to note is if your project's package specifications use Jinja, particularly for scenarios like adding an environment variable or a [Git token method](/docs/build/packages#git-token-method) in a private Git package specification, you should continue using the `packages.yml` file name.

Examine the following tabs to understand the differences and determine when should use to `dependencies.yml` or `packages.yml`.
Examine the following tabs to understand the differences and determine when to use `dependencies.yml` or `packages.yml` (or both at the same time).

<Tabs>
<TabItem value="project" label="When to use Project dependencies">
Expand Down
Loading