-
Notifications
You must be signed in to change notification settings - Fork 52
Closed
Labels
Issue-BugSomething isn't workingSomething isn't workingResolution-FixedThe issue is fixedThe issue is fixed
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
When calling dsc resource get|set|test
and dsc config get|set|test
any errors for the resource list operation bubble up to DSC and block execution, even when the PowerShell group provider isn't being used.
Expected behavior
'{ "scope": "machine" }' |
dsc resource get --resource TSToy.Example/gotstoy
{"ensure":"absent","scope":"machine"}
Actual behavior
'{ "scope": "machine" }' |
dsc resource get --resource TSToy.Example/gotstoy
Error: Operation: Failed to parse resource from provider DSC/PowerShellGroup:
WARNING: There are no modules present in the system with the given module
specification. -> expected value at line 1 column 1
Error details
Error: Operation: Failed to parse resource from provider DSC/PowerShellGroup:
WARNING: There are no modules present in the system with the given module
specification. -> expected value at line 1 column 1
Environment data
Name Value
---- -----
PSVersion 7.3.6
PSEdition Core
GitCommitId 7.3.6
OS Microsoft Windows 10.0.22621
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Version
0.2.0 (build from main)
Visuals
No response
Metadata
Metadata
Assignees
Labels
Issue-BugSomething isn't workingSomething isn't workingResolution-FixedThe issue is fixedThe issue is fixed