You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See #234. Ran in to a bit of confusion as I added an apikey for https://chocolatey.org but it wasn't being used because choco was looking for one for https://chocolatey.org/ (note the trailing slash)
Seems to me some logic could be put in place for looking up stored api keys for sources that perhaps ignores a trailing slash? Not sure what else PowerShell might have in its bag of tricks for URL parsing/equality.
I believe I've encountered a similar issue in NuGet, but the choco team's just a tad bit more responsive ;)
The text was updated successfully, but these errors were encountered:
* stable: (22 commits)
(GH-121) Making Uninstall-ChocolateyZipPackage more robust when
deleting files that were copied during installation of the Zip package
(doc) update changelog/nuspec
(GH-238) ApiKey source matching intuitive
(maint) formatting
(GH-240) Set CredentialProvider for NuGet
(GH-240) ChocolateyNugetCredentialProvider
(GH-240) Add default sources to machine sources
(maint) Only warn subcommand list if not empty
(GH-171) Use RedirectedHttpClient
(GH-240) pass credentials at runtime
(GH-240)(config) Add machine sources
(doc) how to quote values
(GH-230) Export all functions and aliases imported
(GH-230) Fix Issues with Generate/Remove BinFile
(GH-185) Remove console prompt default choices
(GH-186) Uninstall - no prompt for one version
(GH-182) Ask before printing ps1 scripts
(GH-187) Show log file path in messages.
(maint) formatting
(GH-169) Do not resolve disabled sources
...
Conflicts:
src/chocolatey/infrastructure.app/commands/ChocolateySourceCommand.cs
src/chocolatey/infrastructure.app/runners/GenericRunner.cs
See #234. Ran in to a bit of confusion as I added an apikey for
https://chocolatey.org
but it wasn't being used because choco was looking for one forhttps://chocolatey.org/
(note the trailing slash)Seems to me some logic could be put in place for looking up stored api keys for sources that perhaps ignores a trailing slash? Not sure what else PowerShell might have in its bag of tricks for URL parsing/equality.
I believe I've encountered a similar issue in NuGet, but the choco team's just a tad bit more responsive ;)
The text was updated successfully, but these errors were encountered: