-
Notifications
You must be signed in to change notification settings - Fork 3k
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
{Graph} Drop azure-graphrbac
SDK in keyvault module
#22203
Conversation
MSGraph |
return current_user.object_id # pylint:disable=no-member | ||
except CloudError: | ||
current_user = graph_client.signed_in_user_get() | ||
if current_user and current_user.get('id', None): # pylint:disable=no-member |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think id
property should always be there... Any case it won't?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just in case id
doesn't exist. But yes, we might never meet such case😂
A kind reminder.
|
azure-graphrbac
SDK in keyvault moduleazure-graphrbac
SDK in keyvault module
Description
As #22174 mentioned, keyvault module has dependency on
azure-graphrbac
SDK.This PR migrates all the callings from
azure.graphrbac.GraphRbacManagementClient
toazure.cli.command_modules.role._graph_client.GraphClient
And all the related tests have been re-recorded
Testing Guide
Switch to each profile to run all profiles' tests:
az cloud set -n AzureCloud --profile latest
az cloud set -n AzureCloud --profile 2018-03-01-hybrid
And run tests:
azdev test keyvault
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.