Allows setting WinGet proxy setting as SFS Client Proxy#5054
Merged
Conversation
2 tasks
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
JohnMcPMS
approved these changes
Dec 11, 2024
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
2 participants
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.
Allows setting WinGet proxy setting as the SFS Client Proxy.
Fixes the issue below
WinGet download doesn't work through a proxy #5030
This PR requires SfsClient subtree updated to 1.1.0
SfsClient update 1.1.0 for proxy support #5052
Which brings especially
Adding support for a custom proxy input #218
This PR replaces closed PR below
Allows setting WinGet proxy setting as SFS Client Proxy #5032
Microsoft Reviewers: Open in CodeFlow