(GH-165) Ensure null-value nested cim instance arrays are appropriately munged #177
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
Prior to this commit, a null value for a nested CIM instance would not be properly munged into an array. This commit ensures null values for nested CIM instances are munged into arrays with a null value.
michaeltlombardi
changed the title
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 acceptance testing to validate the behavior of nested CIM instances for Puppetized DSC Resources. In the process of writing this acceptance testing, a bug was discovered that prevented the canonicalization of DSC Resource data where a nested cim instance has a value of
$nulland Puppet expects an array.This PR corrects that error and implements acceptance testing validating it.
Resolves #165