Skip to content

identity governance: add remove statements for cmdlets generated for new EM Graph v1.0 APIs #984

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

Merged
merged 2 commits into from
Jan 6, 2022
Merged

Conversation

markwahl-msft
Copy link
Contributor

As we bring APIs for Azure AD entitlement management into Graph v1.0 as part of identity governance, many of the APIs have updated paths. In particular, the beta APIs often used "AccessPackage" as a prefix for resource names, this is not present in the API for v1.0.

As a result, while the suppression rules in Identity.Governance readme.md for the beta APIs continue to be needed for the beta cmdlets which should not be auto-generated, additional rules are needed for the new paths that will be used in Graph v1.0.

This change updates the readme.md with additional rules to reduce the number of Entitlement Management cmdlets that are present in the v1.0 variant of the module. This specifically targets cmdlets which are traversals between two resources. While theoretically possible for a service to implement, the paths that many of these cmdlets emitted were not part of the documented entitlement management API for v1.0 either, so should be suppressed to avoid causing customer confusion.

Note that this change does not include cmdlets for assignment policy or access package resources, as those are not yet in Graph v1.0, a later change will update this readme.md further once those are part of Graph v1.0. Nor does this change update existing custom cmdlets so they are present in v1.0; that will be the subject of a separate change as well.

@peombwa peombwa merged commit c691db1 into microsoftgraph:dev Jan 6, 2022
@markwahl-msft markwahl-msft deleted the mwahl-em-v1rems1 branch January 6, 2022 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants