`az --version` performs an update check

[jessehouwing]

Describe the bug

When running az --version an update check is performed against az-cli and the extensions.

Azure Pipelines' AzureCLI task runs az --version to capture the version details in the logs.

It would save quite a bit of CPU if az-cli would not perform an update check in a CI/CD scenario.

There already is an core.auto-upgrade=false option, would it not make sense to piggy back on that or to add another config setting to turn off update checking.

Related command

az --version

Errors

N/a

Issue script & Debug output

N/a

Expected behavior

No update check is performed in CI.

Environment Summary

2.52.0

Additional context

No response

[yonzhan]

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

[jiasli]

There already is an core.auto-upgrade=false option

According to https://learn.microsoft.com/en-us/cli/azure/update-azure-cli#automatic-update, it should be auto-upgrade.enable=yes.

We do have az version command that doesn't make any network request (#27457 (comment)). I think what you are asking for is an option to disable update check in az --version, while #27457 asks for an option to enable version check in az version. 🤣

[jessehouwing]

Yeah, have a way to disable network access for these commands. Either with an extra parameter to --check-updates true or a setting in the config file or an environment variable.

Ideally az would detect it's in CI/CD and turn off a load of stuff that only adds logspam and slowdowns by default.

It looks like az init is making a start of collecting the desired settings ;).

[jiasli]

az init is actually a secret project. May I know where you heard of it? 🤣

[jessehouwing]

az init is actually a secret project. May I know where you heard of it? 🤣

I was looking for a way to set the default config settings, and I tried it on the console. Lo and behold it downloaded the extension and ran.

I supplied a PR for it to add a few more settings.

[jiasli]

Ideally az would detect it's in CI/CD and turn off a load of stuff that only adds logspam and slowdowns by default.

This is another topic we are still internally investigating. Not only Azure DevOps, we are aiming to find a unified way to detect the running environment - Azure DevOps, Azure Cloud Shell, GitHub Actions, etc.