Enable configuration version tracking for compiled DSC configurations
As a part of infrastructure as code or using DSC in the deployment pipelines, it is desired that we be able to identify the version of the node configuration. With all configurations being put into a source / version control repository, it won't be difficult to promote the version number for a given configuration document. However, at this point in time, there is no way to specify the version of the configuration document itself anywhere. This makes it hard to determine or identify what version of the configuration is being used on a target node without using a 3rd party console or integration into source control.
The ask here is to add support for specifying configuration meta properties such as version of the configuration.
Ravikanth Chaganti
shared this idea
2 comments
-
Ravikanth Chaganti
commented
Agree with that @gaelcolas.
-
gaelcolas
commented
I'd add that Open Sourcing the PSDesiredStateConfiguration.psm1 would be a great enabler to add such features.