Closed JustinGrote closed 4 months ago
Thanks for opening this @JustinGrote -- looks like it might be an issue with the error message
Thanks @JustinGrote looking at this further, want to confirm, was this the command you ran? install-psresource az.accounts -Repository pwshgallery -verbose -debug
And what is the output of Get-PSResourceRepository | fl *
Correct, this is my nuget v3 bridge for PowerShell gallery. The destination is https://pwsh.gallery/index.json
I do also want to note I pushed an update that has tags
as a property but it is an empty array rather than not being present, which works around the issue but per the nuget spec, it should still be an optional property and may be a problem for other third-party v3 nuget repository compatibility
Quite the pickle, was hoping to use this newer module for its supposedly superior authentication mechanisms, but its not abiding by nuget specs. Attempting to use it with TeamCity, and its a no go. Not even the v2 endpoints work! PowershellGet v2.2.5 is so painful when used with authentication, but when used without appears to work "fine" v2/v3 (v3 pre-release semver issues not withstanding).
This might be closable now due to issue #1621 being closed since they have merged in this fix: https://github.com/PowerShell/PSResourceGet/pull/1627
This issue should be resolved via #1627 . If you still see an issue with this please feel free to comment and I can re-open, thanks @JustinGrote !
Prerequisites
Steps to reproduce
Attempt to install a package from a NuGet v3 repository.
However, per the NuGet v3 spec, tags is an optional property, and PSResourceGet should handle the case where tags is present and ignore the tags-based search: https://learn.microsoft.com/en-us/nuget/api/registration-base-url-resource#catalog-entry
Expected behavior
Actual behavior
Error details
Environment data
Visuals
No response