-
Notifications
You must be signed in to change notification settings - Fork 975
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
clarify ado behavior #6705
base: current
Are you sure you want to change the base?
clarify ado behavior #6705
Conversation
this pr clarifies that for ado, private packages have to be configured using the `org/repo` path. more details in internal slack: https://dbt-labs.slack.com/archives/C07C793M6EB/p1734715084356599?thread_ts=1734359013.848149&cid=C07C793M6EB
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
website/docs/docs/build/packages.md
Outdated
``` | ||
|
||
:::tip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe this shouldn't be a callout - can make this expandable or h4?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick turnaround on updating these!
i'd recommend making sure that the bits about org/project/repo are indicated as an ADO concept
For Azure DevOps repositories, you can only specify the `org/repo` path. The project tier is inherited from the source repository currently integrated with dbt Cloud. | ||
|
||
- If the package repository is within the same project as your source repository, you’re in the clear. Simply specify org/repo in the private block. | ||
- If the package repository is not within the same project as your source repository, this feature will not work for you until a future update. | ||
- This currently only works within a single Azure DevOps project. If your repositories are in different projects within the same organization, you can't reference them in the `private` key at this time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add this as a "Prerequisite" of the feature? That, for ADO, the repo is located within the same org/project as your project's repo.
this pr clarifies that for ado, private packages have to be configured using the
org/repo
path.more details in internal slack: https://dbt-labs.slack.com/archives/C07C793M6EB/p1734715084356599?thread_ts=1734359013.848149&cid=C07C793M6EB
🚀 Deployment available! Here are the direct links to the updated files: