Fix blueprint export configuration name #4692
Merged
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.
Pull Request (PR) description
This pull request addresses an issue where the
Assert-M365DSCBlueprint
function would create a GUID for a temporary configuration export and the GUID starts with a digit instead of a letter. The PowerShell configuration parser requires that a configuration name starts with a letter, therefore the call would fail when detecting the configuration and report that the entire configuration has drifted (which is not true).This Pull Request (PR) fixes the following issues