Upgrade msal pip package referred by azure-cli-core to version 1.32.0

[XiangyuL-Tursio]

In the most recent released version of azure-cli-core pip package, a beta version of package msal is referred as a hard requirement. It prevent developer to refer another higher formal version of msal. For example:

ERROR: Cannot install -r requirements.txt (line 2), azure-cli-core==2.71.0 and msal==1.32.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested msal==1.32.0
    The user requested msal==1.32.0
    azure-identity 1.21.0 depends on msal>=1.30.0
    azure-cli-core 2.71.0 depends on msal==1.31.2b1

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Hope the team can loose the version requirement like make it "msal>=1.31.2b1" or at least use the most recent version "msal==1.32.0". Of course the best is to declare "msal>=1.32.0".

Currently, we have no choice but can only use the beta version of msal in our project all arounds.

[yonzhan]

Thank you for opening this issue, we will look into it.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• cli-core: pinning msal to beta in 2.41.0 causes dependency conflict #24373

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

On a general note, please take more care in not pinning dependencies too tightly in setup.py. Dependency hell is not a pleasant place to be in. Users need a bit of leeway with your dependencies because Azure libraries are not used in a vacuum. The requirement.txt file or package installer lock files (pipenv, poetry, flit, ...) are the place to hard-pin dependencies in the pythonic packaging paradigm, not setup.py.

Reference:

• cli-core: pinning msal to beta in 2.41.0 causes dependency conflict #24373 (comment)

Powered by issue-sentinel

[bebound]

Bump to 1.32.0 in #31103, please wait for next release.

[jiasli]

It is recommended to install Azure CLI in a dedicated virtual environment.

You may install msal==1.32.0 in a separate virtual environment so that it doesn't interfere with Azure CLI's requirement.