PowerShell / PowerShell/PSResourceGet

Update-PSResource -Debug inquire?

Open
#1,476 0 comments 0 reactions 1 assignee View on GitHub

@anamnavi is already working on this.

Since Dec 4, 2023.

Area-Update
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

it looks like Update-PSResource -Debug uses inquire

This seems like a regression, it did not work like this in previous release.

Expected behavior
# it should work like -Verbose but output `Debug` info if any is available.
PS 7.4 > Update-PSResource -Verbose
VERBOSE: All paths to search: 'C:\Users\<username>\Documents\PowerShell\Modules'
VERBOSE: All paths to search: 'C:\Users\<username>\Documents\PowerShell\Scripts'
VERBOSE: Package names were detected to be (or contain an element equal to): '*', so all packages will be updated
VERBOSE: Retrieving directories in the path 'C:\Users\<username>\Documents\PowerShell\Modules'
VERBOSE: Retrieving directories in the path 'C:\Users\<username>\Documents\PowerShell\Scripts'
Actual behavior
PS 7.4 > $DebugPreference
SilentlyContinue
PS 7.4 > Update-PSResource -Debug
VERBOSE: All paths to search: 'C:\Users\<username>\Documents\PowerShell\Modules'

Confirm
Continue with this operation?
[Y] Yes  [A] Yes to All  [H] Halt Command  [S] Suspend  [?] Help (default is "Y"):


# it prompts for confirmation with `-Debug`, which differs from `-Verbose`
Error details

No response

Environment data
Get-Module -Name Microsoft.PowerShell.PSResourceGet; $PSVersiontable | Format-Table

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     1.0.1                 Microsoft.PowerShell.PSResourceGet  {Find-PSResource, Get-InstalledPSResource, Get-PSResourceRepository, Get-PSScriptFileInfo…}


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

No response

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.