-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Support internalized package repositories #213
Comments
this should really just be |
Great point, will update |
This might be a duplicate of #118. If you agree, please close this one as a duplicate. If not, feel free to leave this Issue open. |
I don't think having a REST API is the same as supporting these others or intenalzied. The way the rest one is worded could very well just be the/another MSFT repo. |
@JoshPhillips59 support for private sources is available via the REST API. We have provided a reference implementation. We're still working on documentation, and a couple of other features mentioned like Authentication Authn/Authz & MSA. Your last two items should be additional Issues for the reference implementation (you could certainly build a custom interface for those as well). |
Any updates on this? |
Support for internalized package repositories
Rather than rely on a public repo would like to have the option to host the packages via artifactory, or others (necus, proget) in as a remote (like choco does)
Proposed technical implementation details (optional)
Allow me to customize source of winget installs to point to my internal/hosted repo
Ensure it supports the ability to authenticate to said repo
Repo is able to talk to public repo and fetch packages on demand
packages kept up to date on the fly
The text was updated successfully, but these errors were encountered: