Open
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