{Role} Raise GraphError only when Graph request fails
#22523
Merged
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.
Related command
az adDescription
Currently, all subclasses of
CLIErrorare re-raised asGraphError. This is not correct and causes failure forAuthenticationErrorhandling.For example, we change
microsoft_graph_resource_idto an invalid value likehttps://graph1.microsoft.com/, which is then used as ascopeto get an access token:azure-cli/src/azure-cli-core/azure/cli/core/cloud.py
Line 308 in 31e396b
The error handling procedure failed:
This PR makes
send_raw_requestraise a dedicated errorHTTPErrorand it is then re-raised asGraphError. SinceHTTPErroris a sub-class ofCLIError, it is backward compatible.Now invalid
scopewill result in