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

[Feature] Add a private package definition #10083

Closed
3 tasks done
ChenyuLInx opened this issue May 2, 2024 · 0 comments · Fixed by #10084
Closed
3 tasks done

[Feature] Add a private package definition #10083

ChenyuLInx opened this issue May 2, 2024 · 0 comments · Fixed by #10084
Assignees
Labels
enhancement New feature or request

Comments

@ChenyuLInx
Copy link
Contributor

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

dbt-cloud is adding support to allow users to define private packages in their dependencies.yml or packages.yml. The format will be similar to git package definition except that the git field will be the private field and an additional optional provider field. Example:

packages:
  - private: dbt-labs/my-awesome-repo
    # optional configs - same as for 'git' packages
    revision: ... # tag, release, branch, or commit SHA
    subdirectory: ...
	provider: github (if there are multiple providers)

In dbt-core, when such a package is defined, we should provide clear error message and tell user to use git definition.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants