Version dependency issues between powerfulseal and latest azure python libs

[mffiedler]

With the latest azure python libs installed (needed for improved DefaultAzureCredential() API to work correctly):

azure-common 1.1.26
azure-core 1.9.0
azure-identity 1.5.0
azure-keyvault-certificates 4.2.1
azure-keyvault-keys 4.3.0
azure-keyvault-secrets 4.2.0
azure-mgmt-compute 17.0.0
azure-mgmt-core 1.2.2
azure-mgmt-network 16.0.0
azure-mgmt-resource 15.0.0
azure-mgmt-storage 16.0.0

Installing PS at this point uninstalls several of these libs and installs lower versions due to dependency <, >= requirements:

azure-common>=1.1.23,<2.0.0
azure-mgmt-resource>=2.2.0,<3.0.0
azure-mgmt-network>=2.7.0,<3.0.0
azure-mgmt-compute>=4.6.2,<5.0.0

We end up with:

azure-common 1.1.26
azure-core 1.9.0
azure-identity 1.5.0
azure-keyvault-certificates 4.2.1
azure-keyvault-keys 4.3.0
azure-keyvault-secrets 4.2.0
azure-mgmt-compute 4.6.2
azure-mgmt-core 1.2.2
azure-mgmt-network 2.7.0
azure-mgmt-resource 2.2.0
azure-mgmt-storage 16.0.0

Are there known issues preventing bumping the versions of azure-mgmt-compute, azure-mgmt-network and azure-mgmt-resource? Any smoke testing we can help do to validate? For Kraken (http://github.com/openshift-scale/kraken) sandbox and dev testing we are overriding it, but certainly can't do that for real support.

[seeker89]

I don't think there are any blockers for upgrading, other than no one tested with the new major versions. If you guys could do the testing, I'm all for upgrading!