-
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
ModuleNotFoundError: No module named 'azure.identity' in latest CLI (v2.36.0) #22192
Comments
@jiasli for awareness |
You may send your feedback to |
@jiasli Thanks for the info. I attempted adding Installing collected packages: msal-extensions, azure-identity
Attempting uninstall: msal-extensions
Found existing installation: msal-extensions 1.0.0
Uninstalling msal-extensions-1.0.0:
Successfully uninstalled msal-extensions-1.0.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
azure-cli-core 2.36.0 requires msal-extensions~=1.0.0, but you have msal-extensions 0.3.1 which is incompatible.
|
It really feels like these releases should have been coordinated better on the MS/Azure side. Referencing #24188 since that's the issue that will actually "fix" this. Closing here since nothing will be addressed from this repo as best as I can tell. |
@jiasli Unless I missed it, there's no mention of this in the release notes: https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md#april-26-2022 Again, I would reiterate, it really feels like this change and the upcoming change to the Azure SDK for Python should have been communicated and coordinated better. |
Thanks @mikesprague for the feedback. We will certainly work more tightly with Azure SDK team to avoid such kind of issue from happening again in the future. |
Describe the bug
After upgrading to the latest version of the CLI (v2.36.0) I have started receiving the following error:
To Reproduce
Expected behavior
I expected it to find the import and continue processing. The above code works in
v2.35.0
and below.Environment summary
GH Workflow using GH Action
azure/cli@v1
(CLI version v2.36.0). Additional details:Additional context
As mentioned previously, pinning the workflow to
v2.35.0
allows things to work again. I wouldn't expect a breaking change in a minor version update to the CLI so I have to assume this is a bug.The text was updated successfully, but these errors were encountered: