-
Notifications
You must be signed in to change notification settings - Fork 48
Experimental WinPowerShell DSC import extension #1025
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Experimental WinPowerShell DSC import extension #1025
Conversation
@SteveL-MSFT Any idea why the Windows build failed on fetching packages? |
@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. |
…into implement-powershell-import-extension
a9e618e
to
5fdc34d
Compare
…b.com/Gijsreyn/operation-methods into implement-powershell-import-extension
Hi @SteveL-MSFT, this one was a pretty tough one, especially with the latest fixes on the Now there's a conflict between the ones. Is there another indication to tell DSC's engine what extension to use? |
6bdf559
to
f7069cb
Compare
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.