Add DSC Pull Server with Private PowerShell Gallery as a deployment option
With PowerShell gallery coming to on-prem deployments, it will be a source of PowerShell DSC and other modules for all enterprise IT needs. PowerShell gallery uses SQL backend as a module store. There has been an ask to move the existing Pull Server database to SQL. By integrating Pull Server as a deployment option within PowerShell Gallery, the existing SQL store can be used as module and configuration store and eliminates the need for making a copy of all modules on a separate pull server. This also brings in the advantages / well-known deployment models of a typical web application such as the ability to use a clustered backend and load balancers to DSC pull server deployments.
A Twitter poll on this suggested that there is interest in this: https://twitter.com/ravikanth/status/745589610441388032
45 votes on that may not be substantial to decide but an indication.
I second Jordan's NuGet suggestion. Would be nice to utilise on Visual Studio Team Services too.
In the same vein, I would also be interested in a Private Package (NuGet) Repository as a deployment option as well.
Ravikanth Chaganti commented
My note above about SQL backend being the module store is an ask. I understand the nuget packages are inside the app_data folder of the Gallery deployment but the module information itself is in the SQL store.