Open jiasli opened 2 years ago
When packaging an MSI
https://github.com/Azure/azure-cli/blob/99c5fb4cd661ecf157ce2b42cba26c681702305e/requirements.txt#L2
is not honored, so the latest setuptools
is installed.
The new version of cli is completly unusable for me because of this regression. When can we expect this to be fixed? Is the only workaround now to downgrade the azcli?
@mkrzywanski,
The new version of cli is completly unusable for me because of this regression.
How do you define "unusable"?
The latest 2.38.0 Azure CLI still only takes acceptable time (~900ms) to execute. This is still must faster than years ago (~2.3s).
> Measure-Command {az version}
Days : 0
Hours : 0
Minutes : 0
Seconds : 0
Milliseconds : 911
Ticks : 9115245
TotalDays : 1.05500520833333E-05
TotalHours : 0.00025320125
TotalMinutes : 0.015192075
TotalSeconds : 0.9115245
TotalMilliseconds : 911.5245
I have already downgraded to previous version that I used (2.31.0) so cannot check but with 2.37.0 and 2.38.0 it took like 5 seconds for me to get a simple secret value from keyvault. Also refreshing state with terraform took like 3 minutes for new azcli versions and with older versions it is blazingly fast.
it took like 5 seconds for me to get a simple secret value from keyvault.
Could you share the command you used? We can help verify. @evelyn-ys
refreshing state with terraform took like 3 minutes for new azcli versions and with older versions it is blazingly fast.
You way report this issue to https://github.com/hashicorp/terraform-provider-azurerm instead.
It seems with
setuptools
62.6.0 installed,disutils
importssetuptools
andpkg_resources
. This causes some performance regression:Originally posted by @jiasli in https://github.com/Azure/azure-cli/issues/7447#issuecomment-1181600870