Open
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Summary
When using the WinPS adapter, class-based properties don't align with what is happening in the PS adapter. This is because the WinPS adapter uses the Get-DscResource
command from PSDesiredStateConfiguration
, whereas the PS adapter leverages AST. See screenshot:
Steps to reproduce
- Add the
dsc.exe
to the PATH variable - Run
dsc resource get --resource TestClassResource/TestClassResource --input (@{Name = 'test'} | ConvertTo-Json)
- Add the tests folder to PSModulePath
- Run
dsc resource list --adapter Microsoft.Windows/WindowsPowerShell
- Run
dsc resource get --resource TestClassResource/TestClassResource --input (@{Name = 'test'} | ConvertTo-Json)
again
See the output:
Expected behavior
The properties should be the same
Actual behavior
The properties aren't the same
Error details
Environment data
Name Value
---- -----
PSVersion 7.5.1
PSEdition Core
GitCommitId 7.5.1
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
Version
dsc 3.2.0-preview.1
Visuals
No response