identity governance: prepare EM custom cmdlets for v1.0 #990
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
markwahl-msft
requested review from
ddyett,
georgend,
peombwa and
shemogumbe
as code owners
…t, request and catalog
peombwa
approved these changes
Jan 5, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In Azure AD identity governance entitlement management, there are already helper cmdlets for the beta API in the custom subdirectory. This change introduces some cmdlets for v1.0.
List access packages: relationships have new shorter names in v1.0 so filter construction needs to check profile
Get of assignment, assignment request and catalog: these resources have new shorter names in v1.0, this adds new custom files essentially the same as the already-present cmdlets for beta that had the longer names
Get, New and Split of connected organization: allow these to be used for both v1.0 and beta
Note that as the access package assignment policy is not yet a resource in v1.0 API (it's still just in beta), this change does not introduce or update cmdlets referencing policies.