Assert-M365DSCBlueprint: Add support to exclude resources from being compared #3262
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
|
Would it also make sense to add support for it in the New-M365DSCDeltaReport while we're at it? |
…port and Compare-M365DSCConfigurations
|
Sure, just added support for it on both New-M365DSCDeltaReport and Compare-M365DSCConfigurations. |
NikCharlebois
approved these changes
May 3, 2023
NikCharlebois
added a commit
that referenced
this pull request
May 3, 2023
ExcludedResources: Document newly added parameter added on #3262
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.
Pull Request (PR) description
When running Assert-M365DSCBlueprint one might want to just compare policies and not content resources such as AADUser, AADGroup, SPOSite, etc. This PR adds a new parameter to the function which allows to exclude certain types of resources from the report.
As an example these resources could be excluded from being compared:
Additionally the function now throws an exception if ConvertTo-DSCObject fails, this is based on the issue #3259 I raised a couple of hours ago.