PowerShell / PowerShell/PSResourceGet

`Save-PSResource` fails when targeting Artifactory with `-Version` (`NormalizedVersion` issue)

Open
#1,689 0 comments 1 reaction 1 assignee View on GitHub

@alerickson is already working on this.

Since Aug 27, 2024.

Area-Save Needs-Triage
Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest released version
  • Search the existing issues.
Steps to reproduce
  1. Attach PSResourceGet to Artifactory repository
  2. Publish module to repository with Publish-PSResource
  3. Save the published module with Save-PSResource, specifying the version of the module with -Version
Expected behavior
PS> Save-PSResource -Name MyModule -Version 0.10.2
PS> # No error
Actual behavior
PS> Save-PSResource -Name MyModule -Version 0.10.2
Save-PSResource: Package(s) 'MyModule' could not be installed from repository 'Artifactory'.
PS>
Error details
N/A
Environment data
ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     1.0.5                 Microsoft.PowerShell.PSResourceGet  {Find-PSResource, Get-InstalledPSResource, Get-PSResourceRepository, Get-PSScriptFileInfo…}


Name                           Value
----                           -----
PSVersion                      7.4.4
PSEdition                      Core
GitCommitId                    7.4.4
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Visuals

Running with -Verbose suggests that PSRG is using NormalizedVersion in $filter on a call to FindPackagesById(). Because Artifactory doesn't calculate this property for packages hosted on the service itself, the call returns no results and Save-PSResource fails.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.