Open sean-r-williams opened 1 month ago
I see three options here:
$filter=IsLatestVersion
works as expected for this package (i.e. fix PowerShell/PowerShellGallery#273)@alerickson @SydneyhSmith This bug isn't something I can directly contribute a fix for since we're running up against [unexpected] behavior in the Gallery.
Can someone from your team take a look here?
We originally engaged JFrog support for this and have some line of dialogue with their R&D. (JFrog folks, see ticket #296792) If we need to get adjustments made in JFrog to align its behavior with other servers (thus obviating the need for quirk flags in this space), now would be an excellent time to do so.
Alternatively, if your team is comfortable with munging the filter (i.e. convert from IsLatestVersion
to IsLatestVersion eq true
, add a space to the front of the string, etc.), I can cut a PR for that (with the understanding that it will decrease legibility of the codebase).
As mentioned in this issue, we're going to look into the Gallery codebase to see what is happening and if we can't safely make the change there then we'll open a fix client side.
Prerequisites
Steps to reproduce
v2
).Update-PSResource Microsoft.PowerShell.PSResourceGet
.Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
This seems to be the combination of two separate issues:
FindPackageById()
if we detect the upstream repo is a JFrog repo. After discussing with JFrog support, they confirmed that NuGet calls like this are being passed unfettered to the upstream. This means that PSGallery is receiving subtly different API call parameters when it's being reflected through Artifactory.IsLatestVersion
, is returning unexpected results. I filed PowerShell/PowerShellGallery#273 to track this.