BREAKING: Add Key Identifiers to CIM instances #6784
Conversation
This file contains hidden or 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
FabienTschanz
requested review from
M365DSCApprover,
NikCharlebois,
m365dscapproval and
ykuijs
as code owners
FabienTschanz
force-pushed
the
ref/cim-key-identifiers
branch
from
5b7eefd to
7ea66e6
Compare
FabienTschanz
changed the title
FabienTschanz
force-pushed
the
ref/cim-key-identifiers
branch
from
7ea66e6 to
49aaf78
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR adds key identifiers to all CIM resources where applicable. If any property contains CIM instances on arrays, and an individual CIM instance contains at least one identifier or any property that makes the instance unique, it is now required to have one of them. This massively helps in comparison and drift reporting.
This Pull Request (PR) fixes the following issues
None.
Task list
Entry should say what was changed and how that affects users (if applicable), and
reference the issue being resolved (if applicable).