Experimental WinPowerShell DSC import extension

[Gijs Reijn (Gijsreyn)]

PR Summary

This PR introduces a Windows PowerShell DSC import extension that enables the passing in of PSDSC v2 configuration documents.

PR Context

The PR adds three new files to the build:

• convert-resource.ps1
• convertDscResource.psd1
• convertDscResource.psm1

When a user passes in a .ps1 file with a valid DSC configuration document, an attempt is made to convert it by borrowing content from DSCParser.

[Gijs Reijn (Gijsreyn)]

Steve Lee (@SteveL-MSFT) Any idea why the Windows build failed on fetching packages?

[Steve Lee (SteveL-MSFT)]

Gijs Reijn (@Gijsreyn) I'd hold off on this for now, I'm working on a big PR to fix the Windows CI. Basically there was one issue in a test which caused Pester to crash so even though Windows tests have been failing, it was never reported. Since making that fix, many existing tests are failing which I'm now fixing one by one.

[Gijs Reijn (Gijsreyn)]

Hi Steve Lee (@SteveL-MSFT), this one was a pretty tough one, especially with the latest fixes on the build.ps1 script. Yet, I had a successful run at: https://github.com/PowerShell/DSC/actions/runs/16867533276. Then I thought it should be relatively easy to include pwsh.exe as well, which I have now done. However, this raised another issue because both extensions accept .ps1.

Now there's a conflict between the ones. Is there another indication to tell DSC's engine what extension to use?

[Gijs Reijn (Gijsreyn)]

Closed as discussed at the working group; not to be implemented here.