Please allow for versioned configurations in Azure Automation
It would be great to have multiple versions of DSC configurations compiled into Azure Automation, simultaneously.
Currently, a server, or other resource, could be provisioned with one version of a configuration, but if an updated version is compiled during pipeline transitions, they could receive a different configuration than tested in a lower environment, invalidating their tests.
This would allow someone to target a v1.1.0 configuration, even though the latest is v1.1.3 in Azure Automation, for example.
It would be doubly nice if this could be derived from Git tags or other versioning mechanism in TFS/VSTS, as well.
Thank you for his feedback. This is an area we are planning to deliver in the future.
its been 4yrs promising source control integration for configuration like runbooks, whats the hang up?
Ralph S commented
Great idea! Would provide much needed flexibility for development.