Replies: 1 comment
|
Some packaging clients (like NuGet) automatically pick up default Windows credentials for on-prem feeds, so artifacts-credprovider isn’t needed in those cases. This comment is likely referring to scenarios where clients don’t do this by default. However, even then, I can’t think of a situation where installing artifacts-credprovider, setting feed endpoint URLs with a PAT, and manually rotating that env variable would be simpler than just configuring the client directly with the PAT. For pipeline scenarios, the NuGetAuthenticate task essentially sets up and configures artifacts-credprovider to run in build mode, so future restores can authenticate without extra steps. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
From the README.md
https://github.com/microsoft/artifacts-credprovider?tab=readme-ov-file#azure-devops-server
Under which conditions is it required?
Is it only this from the README.md?
All reactions