[vcpkg] Remove hard-coded ApiKey from nuget push #14202
Merged
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.
Describe the pull request
After experimenting with vcpkg binary caching feature and trying to upload the built binaries to GitHub Packages using NuGet, I ran into a similar authentication issue as #12984.
This PR removes the hard-coded NuGet API key so that a user's specified key can be used in a
VCPKG_BINARY_SOURCES
environment variable.This was my first time using NuGet and setting everything up with GitHub Packages, so if this hard-coded key name is somehow intentional, I'd like to know how to work around this or what a better binary caching setup would look like.
What does your PR fix?
Fixes nugetconfig binary source ignores API key in config file #12984
Which triplets are supported/not supported? Have you updated the CI baseline?
N/A
Does your PR follow the maintainer guide?
Yes.