-
Notifications
You must be signed in to change notification settings - Fork 909
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
Allow to reuse nuget credentials for choco #2221
Comments
Patch should be trivial, e.g.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's possible to host nuget/choco packages on private feed in azure devops.
Private means that it also requires authentication to list, download or install any package from that feed.
Theoretically you can use choco's approach to configure credentials to azure devops -
https://docs.chocolatey.org/en-us/create/commands/api-key
and provide user name as login and azure devops Personal Authentication Token (PAT) as password.
From software developer perspective however - it's easier just to configure credentials once for both - nuget packages and for choco packages in one place and use them for all eternity (that is 1 year as long as PAT is valid).
You can configure and store nuget credentials in centralized manner - that is using
%APPDATA%\NuGet\nuget.config
folder.(Instructions can be found from here for example: https://mallibone.com/post/private-nuget-feed-azure-devops )
It would simplify whole picture if choco could re-use same kind of credentials as nuget uses - that is same config file.
Based on my brief analysis there needs to be implemented two features:
https://....azure.com/.../nuget/v3/index.json
=>https://....azure.com/.../nuget/v2
Azure devops supports older communication protocols, which is used by choco - v2. Maybe choco can translate those url automatically (throw away v3... part and put v2 instead) - this is needed not only for command line, but also for url stored in nuget.config.
%APPDATA%\NuGet\nuget.config
- if that file exists.Using this approach it's possible to configure nuget and choco in centralized manner and use both as necessary.
The text was updated successfully, but these errors were encountered: