Officially release more DSC Resources
We only have around 12 officially released DSC resources. I had expected PowerShell V5 would include more officially supported resources, but it was not to be. Please releae them, preferably via Windows Update.
What would you describe as “official”? We are moving forward with some of the x-named DSC resources in the Gallery, with the intent of removing the x and fully supporting them once they hit a certain level of quality. Is that sufficient?
Brett Hamilton commented
Thanks for the update @J.Keith.
Justin King commented
Thomas: It's not pre-packaged software. It's standardized PS1 scripts accessing WMI. Anyone, right now, can open xNetworking in notepad and hack away at it (use ISE please). Thinking of modules as "when will they officially supported" is like asking some random poster of a blog to support his script he used to get some work done.
Right now, this moment, I have posted three separate modules on PSGalllery. Anyone can post to it, you're just misinformed if you think psgallery modules are _ever_ going to be supported by Microsoft. It's a centralized repo, nothing more.
But honestly I'm just echoing what a Microsoft rep has said on GIthub around the modules/resources: the "x/c/whatever" is being deprecated.
Don't hold your breath for anything beyond critical/core resources. What you're asking for is currently contrary to their entire marching direction.
Justin: many large organisations (and some small ones) only ever use fully supported and released software. A DSC resource should be no different. There are already some 'relased' resources (https://msdn.microsoft.com/en-us/powershell/dsc/builtinresource). As to community suppoted - I love the concept, but customers pay for released code (and for supporting released code). What happens when a PSGallery item has a bug - Does MS just say 'not ours - too bad'???
Thinking more about this, what I'd like to see is two things:
1. The 'official' or 'released' resources should be capable of being seen with Get-DSC resource. The released resources should be added to the PSDesiredStateConfiguration module which should be updated each time new resources are officially launched.
2. The names of these newly released resources and fully supported resources should be added to the page: https://msdn.microsoft.com/en-us/powershell/dsc/builtinresource
Justin King commented
DSC resources are being shipped/updated via the power-shell gallery and maintained via GitHub completely separate as they've been made open source.
On the powershell github I was told all "x" and "c" where soon going to be dropped because it's community supported now.
Put the two together and modules are becoming 100% community driven ... I don't think "official" has any context anymore.
That would work nicely. At the same time, I'd like to see the DSC Resources ship with Windows Server and be provided via WIndows Update.