Closed valainisgt closed 8 months ago
After some more digging this same issue was uncovered back in 2020 with PowerShell/PSDesiredStateConfiguration#73. I will close this issue if PowerShell/PSDesiredStateConfiguration#73 sufficiently covers what is wrong.
Closing because this was fixed in 2.0.6
Prerequisites
Steps to reproduce
I am experiencing a problem with the PSDesiredStateConfiguration 2.0.5 module. The
Get-DscResource
function does not return the correct resources when run on windows. The privateGet-DscResourceModules
function splits the current PSModulePath using a colon instead of the platform specific path separator, which I believe to be the problem.I have created a repository that demonstrates the problem. The repository has an xUnit.net test project that outlines a couple of scenarios showing the error. I have also documented a potential fix for the issue in the repository at this commit.
Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
No response