PowerShell DSC, along with Windows Server 2012 R2 has reached General Availability! Â Yay!
However, there is (at least one so far) breaking changeÂ in Desired State Configuration (DSC).
Fortunately, the change is in an area I haven’t blogged about yet.. creating custom resources. Â Unfortunately, it does mean I’ll have to update the GitHub repositoryÂ and all my internal content (should be done by early next week).
The short version is that DSC resources are now resources inside modules, rather than each resource being independent modules. Â The benefit of this is that now DSC resources won’t pollute the module scope, each resource won’t need its own psd1 file (the source module will require one though), and it provides an easier way to group resources, which wasn’t really possible before.
So, with GA, resources should go under the module root in a folder DSCResources. Â You can have one or more resources in one PowerShell module. Â The PowerShell module version is what will be used for the resource version number, so if you have several resources, a version number bump affects all the resources in the module.
I’ll be picking back up with the DSC series next week with how to configure DSC clients, so stay tuned.