Add configuration validation during parsing #59
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds validation of the
ParseErrorswhen runningParseInputon the supplied content inConvertTo-DSCObjectwhile ignoring errors about the Microsoft365DSC module in version XYZ not being present and that a resource in the configuration is not defined. This is done to ensure that even "outdated" configurations can still be parsed even though a newer version of Microsoft365DSC already exists.To not break the flow, it only outputs a warning message stating that the configuration contains errors and which part of the configuration contains the error. No throw statement is included.