Work around dotnet tool exec auth failure on private NuGet feeds#7347
Merged
Work around dotnet tool exec auth failure on private NuGet feeds#7347
Conversation
dotnet tool exec has a known bug (dotnet/sdk#51375) where it fails to authenticate against private NuGet feeds, returning 401 even when credentials are properly configured. Replace dotnet tool exec with dotnet tool install --tool-path + direct execution, which handles authentication correctly. Tool-paths are version-specific to avoid file-lock conflicts during parallel execution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dotnet tool execwithdotnet tool install --tool-path+ direct execution to work around dotnet/sdk#51375, wheredotnet tool execfails to authenticate against private NuGet feeds (401 Unauthorized)dotnet tool installhandles NuGet authentication correctly; the tool is installed to a persistent version-specific path (~/.dotnet/rewrite-tools/<version>/) so multiple versions can coexist without file-lock conflicts during parallel executionTest plan
dotnet tool install --tool-path+ direct execution works with empty cache (fresh install)--add-sourcewhen available