`Update-PSResource *` seems stuck in nuget repo

[SteveL-MSFT]

Prerequisites

• [X] Write a descriptive title.
• [X] Make sure you are able to repro it on the latest released version
• [X] Search the existing issues.

Steps to reproduce

update-psresource * -verbose

Expected behavior

Expect all installed resources to try to get updated

Actual behavior

When it hits the nuget repo, it repeats and doesn't seem to end:


VERBOSE: No packages found in repository: NuGet.


Seems like we should have some progress written during discovery and actual updating

Error details

N/A

Environment data

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     3.0.16     beta16     PowerShellGet                       {Find-PSResource, Get-PSResource, Get-PSResourceRepository, Install-PSResource…}

Name                           Value
----                           -----
PSVersion                      7.3.0-preview.6
PSEdition                      Core
GitCommitId                    7.3.0-preview.6
OS                             Darwin 21.6.0 Darwin Kernel Version 21.6.0: Sat Jun 18 17:05:47 PDT 2022; root:xnu-8020.140.41~1/RELEASE_ARM64_T8101
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[SydneyhSmith]

Currently the Name parameter defaults to * we need to decide if this is the correct behaviour

[SteveL-MSFT]

From team discussion, part of the problem is Update-PSResource * may update to newer versions that the user doesn't want. For example, if the user is on 1.0.1, they may only want to update to 1.0.x or optionally to 1.x.y. This assumes semver is being respected. So we need to think through more of the bulk update scenario on both what the user can control and what the defaults should be (I would suggest the safest updates by default so only to newest patch version and not even newer minor version). For the 3.0 release, it may make sense to not allow wildcards so that we can have more time to design for 3.1