`PSResourceList` set operation fails when warning contaminates stdout JSON

Aperta
#1,999 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@adityapatwardhan ci sta già lavorando.

Dal 6/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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

On a fresh Windows Server 2025 box, the Microsoft.PowerShell.PSResourceGet/PSResourceList DSC resource fails during a set operation. This is because by default the modules path isn't added to the PATH throwing a warning like:

The installation path for the script does not currently appear in the CurrentUser path environment variable. To make the script discoverable, add the script installation path, C:\Users\vmadmin\Documents\PowerShell\Modules, to the environment PATH variable.

Because PSResourceGet runs cmdlets in the same runspace as the script, the warning reaches the stdout pipe that DSC reads as JSON, causing the verification step to fail.

To reproduce the issue, create a fresh Windows Server 2025 box (I used Azure) and run:

$in = @'
$schema: https://aka.ms/dsc/schemas/v3/bundled/config/document.json
resources:
  - name: Install required modules
    type: Microsoft.PowerShell.PSResourceGet/PSResourceList
    properties:
      repositoryName: PSGallery
      trustedRepository: true
      resources:
        - name: Pester
          version: 5.7.1
        - name: PSScriptAnalyzer
          version: 1.25.0
'@
dsc config set --input $in 
Expected behavior
Return result through `dsc.exe`.
Actual behavior
See message above
Error details

Environment data
ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Binary     1.3.0      preview1   Microsoft.PowerShell.PSResourceGet  Core,Desk {Compress-PSResource, Find-PSResource, …

Key   : PSVersion
Value : 7.6.2
Name  : PSVersion


Key   : PSEdition
Value : Core
Name  : PSEdition


Key   : GitCommitId
Value : 7.6.2
Name  : GitCommitId


Key   : OS
Value : Microsoft Windows 10.0.26100
Name  : OS


Key   : Platform
Value : Win32NT
Name  : Platform


Key   : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0…}
Name  : PSCompatibleVersions


Key   : PSRemotingProtocolVersion
Value : 2.4
Name  : PSRemotingProtocolVersion


Key   : SerializationVersion
Value : 1.1.0.1
Name  : SerializationVersion


Key   : WSManStackVersion
Value : 3.0
Name  : WSManStackVersion
Visuals

No response

Lingua principale
C#
Stelle
576
Fork
114
Merge medio
1g 2h
PR unite (30g)
7

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PowerShell/PSResourceGet

Tutte le issue di PowerShell/PSResourceGet

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.