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

packages can be specified in dependencies.yml #3550

Closed
1 task
Tracked by #3362
MichelleArk opened this issue Jun 15, 2023 · 0 comments · Fixed by #3577
Closed
1 task
Tracked by #3362

packages can be specified in dependencies.yml #3550

MichelleArk opened this issue Jun 15, 2023 · 0 comments · Fixed by #3577
Assignees
Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows

Comments

@MichelleArk
Copy link
Contributor

MichelleArk commented Jun 15, 2023

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/docs/build/packages#how-do-i-add-a-package-to-my-project

What part(s) of the page would you like to see updated?

Document dependencies.yml and that packages can be set as part of dependencies.yml

Additional information

No response

@MichelleArk MichelleArk added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear dbt-core v1.6 Docs impact for the v1.6 release (July 2023) labels Jun 15, 2023
@jtcohen6 jtcohen6 self-assigned this Jun 20, 2023
@runleonarun runleonarun added the priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows label Jun 22, 2023
jtcohen6 added a commit that referenced this issue Jul 13, 2023
resolves #3550
resolves #3632
resolves #3574

## What are you changing in this pull request and why?

Create a new page for "cross-project `ref` under `collaborate >
govern`. I've decided to call the page "Project dependencies," and use
it as an opportunity to highlight the differences between project +
package dependencies.

I started tackling two closely related issues, since we should be
thematically consistent across all of them:
- `enforce_access` for packages <> model access
- `packages` can be configured in a file named `dependencies.yml` 

## Previews

- [Project
dependencies](https://deploy-preview-3577--docs-getdbt-com.netlify.app/docs/collaborate/govern/project-dependencies)
- [Packages: How do I add a package to my
project?](https://deploy-preview-3577--docs-getdbt-com.netlify.app/docs/build/packages#how-do-i-add-a-package-to-my-project)
- [Model access: How do I ref a model from another
project?](https://deploy-preview-3577--docs-getdbt-com.netlify.app/docs/collaborate/govern/model-access#how-do-i-ref-a-model-from-another-project)
- [dbt_project.yml:
restrict-access](https://deploy-preview-3577--docs-getdbt-com.netlify.app/reference/dbt_project.yml)
- [Upgrading to
v1.6](https://deploy-preview-3577--docs-getdbt-com.netlify.app/guides/migration/versions/upgrading-to-v1.6)

## Checklist
- [x] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [x] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):
- [x] Add page to `website/sidebars.js`
- [x] Provide a unique filename for the new page

---------

Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants