kwirkykat
commented
7 years ago @andy1547 We transfer fixes between the two repositories when we find it appropriate. The two modules are fundamentally the same right now, but they may not stay that way. We have some policy differences between the two:
- xPSDesiredStateConfiguration can be used with WMF 4+ and should probably stay backwards compatible as long as possible. PsDscResources only works with WMF 5.1+ so it can get updates that may not be able to go in xPSDesiredStateConfiguration.
- We also allow breaking changes in xPSDesiredStateConfiguration whereas it is much much harder to get a breaking change into PsDscResources.
johlju
I'm currently having to implement this manually using the Script Resource with sc.exe, however the TestScript resource is really hacky relies on parsing standard output from sc.exe qfailure "MyService", unfortutantly the Get-Service cmdlet is missing many of the ScriptProperties required to test the state (such as FirstFailure, SecondFailure) on Windows Server 2012 R2 Foundation PS 5.1 (works on Windows 10).
There is a Carbon resource for this but it does not support supplying arguments to the service execution path. Has anybody else tackled this issue?
Out of curiosity, what is the process for merging bugs/features from the xPSDesiredStateConfiguration to PSDscResources and vice versa? It seems like all of the bugs/missing essential features I've encountered apply to both repositories.