multiple powershell module versions in automation module
We can't have multiple version of a powershell module in automation.
We develop some DSC resources and we using in different configuration of project but sometime we havnt the same version in each configuration. Like old configuration for project1 with xPSDesiredStateConfiguration with 188.8.131.52 and new configuration for project2 with xPSDesiredStateConfiguration version 184.108.40.206 .
So each time we want to compile we need to upload the old or new version. It's not working like a nugget server keeping old version.
this would also help with rolling out upgrades to modules too, it would be easier to target individual or groups of nodes for test. At present a separate automation account is the only way as @Alex says. It becomes even more critical once you start using composite resources to layer configurations, some of these composites, for instance those covering 'base server' settings potentially touch many machines in the environment, testing is one safety net, but having versioned controlled modules would be great.
Bart Danse commented
We still have some windows 2008 vm's.. (I know..) Because of this we can not upgrade xPSDesiredStateConfiguration. Only way around this is to introduce an additional automation account.
We need support for referencing specific versions of PowerShell modules.
Currently Azure Automation only keeps the latest.