find-psresource [ 3.0.0-beta10] not listing all modules with artifactory repository

Running find-psresource has strange behaviour when the NUGET repository is hosted in Artifactory

Our repository, 'powershelf', has 760 artifacts over 53 unique modules. I can list all of them with version 2.2.5

With powershellget beta, I only see 4

PS 5.1 with PowerShellGet 2.2.5:

ps:\> (find-module -repository powershelf -Credential $creds).count 

53

PS 7.1.0-rc.1 with PowerShellGet 3.0.0-beta10:

ps:\> (Find-PSResource -Repository powershelf -Credential $creds).count
4

When I search for a specific module not listed within the generic find, I get my module just fine.

Additional odd behavior, when Publishing with the publish-psresource, I can not find it by name, only with no name specified, or a * specified for the name. This resolves after about 30 minutes, may be a caching issue

Adrian (@adrian-andersson)

Thanks Adrian (@adrian-andersson) we havent finished the wildcard implementation for v3 nuget feeds (like artifactory) so this likely what is causing the issue. We are interested that 4 made it through--it would be interesting to know if there is some commonality between those 4 that are returned....we have a few theories as to what may be happening (it may only be hitting the first layer of the repository index) but this would help us diagnose the issue...thanks!

Sydney Smith (@SydneyhSmith)

Hi Sydney Smith (@SydneyhSmith) I did a comparison and noted that find-psresource command is returning the first 4 modules in alphabetical order, and I can get the same result with find-module -repository powershelf -Credential $creds|sort-object -Property name |select-object -first 4

Happy to close and revisit this at a later date

Adrian (@adrian-andersson)

Thanks Adrian (@adrian-andersson) we still plan to address this

Adrian (@adrian-andersson)

Hi Adrian (@adrian-andersson), is this still an issue with the latest preview?

Steven Bucher (@StevenBucher98)

Thanks Steven Bucher (@StevenBucher98)

Seems in this beta, with Find-PSResource -name is now a mandatory param. Wildcards don't seem to work with Artifactory repositories with nuget feeds v2 or v3 though. As a result, Unable to 100% verify this is resolved. It works for psgallery though.

Wildcards on artifactory feeds is a pretty big mess. Example using my artifactory repo (Powershelf) and comparing to PSGallery:

Wildcards are clearly not working. It might be an artifactory limitation so I will keep experimenting

get-module powershellget

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     3.0.12     beta       PowerShellGet                       {Find-PSResource, Get-PSResource, Get-PSResourceR…

ps:\> find-psresource -Repository psgallery -Name carb*

Name                     Version  Prerelease Repository Description
----                     -------  ---------- ---------- -----------
Carbon                   2.11.0.0            PSGallery  Carbon is a PowerShell module for automating the configuration…
Carbon.Core              1.0.0.0             PSGallery  Functions that make doing things in PowerShell a little easier…
Carbon.Cryptography      2.2.0.0             PSGallery  Makes encrypting and decrypting strings and other security wor…
Carbon.Windows.Installer 1.0.0.0             PSGallery  The Carbon.Windows.Installer module is a Windows-only module t…


ps:\> find-psresource -Repository powershelf -Name carb* -Credential $creds

ps:\> find-psresource -Repository powershelf -Name carbon -Credential $creds

Name   Version Prerelease Repository Description
----   ------- ---------- ---------- -----------
Carbon 2.9.4.0            powershelf Carbon is a PowerShell module for automating the configuration Windows 7, 8, 2008, and 2012 and automation the installation and configuration of Windows applications, websites, and services. It can …

ps:\> find-psresource -Repository powershelf -Name * -Credential $creds

Name   Version Prerelease Repository Description
----   ------- ---------- ---------- -----------
Carbon 2.9.4.0            powershelf Carbon is a PowerShell module for automating the configuration Windows 7, 8, 2008, and 2012 and automation the installation and configuration of Windows applications, websites, and services. It can …

ps:\> find-psresource -Repository powershelf -Name psrapid -Credential $creds

Name    Version Prerelease Repository Description
----    ------- ---------- ---------- -----------
psrapid 1.0.2.0            powershelf A PowerShell API Framework

ps:\> find-psresource -Repository powershelf -Name psrap* -Credential $creds

Chris Thompson (@aproposts)

Chris Thompson (@aproposts) Chris Dent (@indented-automation) could you let us know the url for your registries?
Also are any packages at all being returned?

alerickson

Sorry for the slow reply, I saw alerickson's question last week then got busy and forgot.

https://gitlab-internal.domain.com/api/v4/projects/135/packages/nuget/index.json

No packages are returned when using wildcards, but can be found if the exact name is given.

Anam Navied (@anamnavi)

Anam Navied (@anamnavi) we should test this with your changes in #1144

Find all was not supported for v3 repositories because many have upstreams which could have expensive unintended consequences, additionally there was not native api support so we prioritized getting base features working before adding the customization logic for v3 support. We can special case for artifactory (and other repos) and plan to do this-- just need to finish up a few other bugs first 😄

Would love to know from folks on this issue if you expect upstream sources to be picked up in a find all call?

Sydney Smith (@SydneyhSmith)

Hi Sydney Smith (@SydneyhSmith) I have switched roles/companies, no longer have access to Artifactory to test, sorry!.

FWIW, I can get a (partial) list of modules from a GitHub Repo iff I specify the Name with one or more letters followed by a wildcard. For example:

Find-PSResource -Repository MyRepo -Name A*

I'm running PowerShell v7.3.8. Below are my package management-related versions:

Microsoft.PowerShell.PSResourceGet 1.0.0
Microsoft.PowerShell.SecretStore 1.0.6
PackageManagement 1.4.4
Microsoft.PowerShell.SecretManagement 1.1.2
PowerShellGet 3.0.22 beta22

(I realize this isn't Artifactory, but it may be related.)

Over a year later meanwhile with AzureDevops Artifact feed, using latest release (1.0.6) of PSResourceGet, can't use any wildcards at all using v3 endpoint:

>Find-PSResource -Repository CustomFeedv3 -Name * -Credential $RepoCred
Find-PSResource: Find all is not supported for the V3 server protocol repository 'PFMLCustomFeedv3'

[...]
Find with Name containing wildcards is not supported for the V3 server protocol...

However, registering a PSResource repo w/ v2 at least allows a partial wildcard:

Find-PSResource -Repository CustomFeedv2 -Name M*

for instance works, assuming "MyFirstModule" or whatever exists.

Still an open issue it seems with Microsoft.PowerShell.PSResourceGet version 1.2.0 . Is there an actual roadmap to deliver this?

Navigation Menu

Repository navigation

find-psresource [ 3.0.0-beta10] not listing all modules with artifactory repository #304

6 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

find-psresource [ 3.0.0-beta10] not listing all modules with artifactory repository #304

Description

Activity

SydneyhSmith commented on Nov 19, 2020

adrian-andersson commented on Nov 24, 2020

SydneyhSmith commented on Dec 10, 2020

StevenBucher98 commented on Jan 5, 2022

adrian-andersson commented on Jan 10, 2022

6 remaining items

alerickson commented on Oct 13, 2022

aproposts commented on Oct 21, 2022

alerickson commented on May 26, 2023

SydneyhSmith commented on Jul 13, 2023

SydneyhSmith commented on Jul 18, 2023

adrian-andersson commented on Jul 19, 2023

rickandersen-forte commented on Oct 13, 2023

OranguTech commented on Nov 18, 2024

shockogit commented on Sep 9, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions