Enable proactive validation of partial configuration MOFs
Votes from Connect: 15
Original Date Submitted: 9/15/2015 8:25:40 PM
Site Name: PowerShell
Feedback ID: 1792984
Currently, the only validation of partial configuration MOFs is in the client (LCM). If multiple MOFs are combined and there's a duplicate key situation, the LCM ceases processing. Having this happen on the target node - with no proactive change to catch the problem - is extremely undesirable, and doesn't set the stage for top-level manageability.
I suggest refactoring that logic from the LCM into a standalone API. The LCM could then call that API to do its current validation - after all, the target node IS the final point where the rubber meets the road. However, that same API could be implemented on a pull server, enabling a consolidated place for validation and problem logging. Ideally, a client would submit its request for all MOFs from that pull server, let the pull server combine and validate them, and then deliver a single combined MOF to the client.
The above would not resolve situations involving multiple pull servers. However, the same API could be wrapped in a "Validate-PsDscMof" command. Given multiple MOF files, it (a) could combine them, (b) produce the combined MOF, (c) indicate any duplicate key or other validation errors, and (d) produce a list of resources that would be required to implement the combined MOF. Such a command/API could become the basis for more "intelligent" pull servers in the future, and would enable proactive testing and validation of complex, partial configurations. It would essentially enable a "resultant set of configuration" capability for diagnostics, if nothing else.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 1792984 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1792984).
Internal BugId: 15815