Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare-M365DSCConfigurations: Problem since 1.23.809.1 #3632

Closed
ricmestre opened this issue Sep 1, 2023 · 0 comments · Fixed by #3633 or #3651
Closed

Compare-M365DSCConfigurations: Problem since 1.23.809.1 #3632

ricmestre opened this issue Sep 1, 2023 · 0 comments · Fixed by #3633 or #3651
Labels
Bug Something isn't working Core Engine

Comments

@ricmestre
Copy link
Contributor

Details of the scenario you tried and the problem that is occurring

On release 1.23.809.1 the cmdlet Compare-M365DSCConfigurations was updated on PR #3526 to fix #3478, nevertheless due to a typo it actually made it worse since for instance running Assert-M365DSCBlueprint will now report drifts that clearly aren't.

Verbose logs showing the problem

Suggested solution to the issue

Fix typo in name of variable in M365DSCReport.psm1:L888

The DSC configuration that is used to reproduce the issue (as detailed as possible)

N/A

The operating system the target node is running

Win10

Version of the DSC module that was used ('dev' if using current dev branch)

1.23.809.1 (later versions still have same issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Core Engine
Projects
None yet
2 participants