az bicep upgrade produces no output

[onionhammer]

Describe the bug

This happens whenever a new version of bicep comes out, but this time it's gone on for multiple days

Whenever a new version comes out, you run 'az bicep upgrade' and either A) It installs the new version or B) it does nothing.

> az bicep version  
A new Bicep release is available: v0.26.54. Upgrade now by running "az bicep upgrade".
Bicep CLI version 0.25.53 (c0ad57dff6)

> az bicep upgrade
> 

Related command

az bicep upgrade

Errors

No errors are shown by default

Issue script & Debug output

cli.knack.cli: Command arguments: ['bicep', 'upgrade', '--debug']
cli.knack.cli: init debug log:
Enable color in terminal.
cli.knack.cli: Event: Cli.PreExecute []
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x000002379654B9C0>, <function OutputProducer.on_global_arguments at 0x00000237966D6160>, <function CLIQuery.on_global_arguments at 0x0000023796703CE0>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: Modules found from index for 'bicep': ['azure.cli.command_modules.resource']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name Load Time Groups Commands
cli.azure.cli.core: resource 0.079 51 228
cli.azure.cli.core: Total (1) 0.079 51 228
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_ai_examples', 'azext_next']
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name Load Time Groups Commands Directory
cli.azure.cli.core: Total (0) 0.000 0 0
cli.azure.cli.core: Loaded 51 groups, 228 commands.
cli.azure.cli.core: Found a match in the command table.
cli.azure.cli.core: Raw command : bicep upgrade
cli.azure.cli.core: Command table: bicep upgrade
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x0000023799556E80>]
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to '.azure\commands\2024-03-15.09-38-56.bicep_upgrade.52368.log'.
az_command_data_logger: command args: bicep upgrade --debug
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument..add_subscription_parameter at 0x00000237995B13A0>]
cli.knack.cli: Event: CommandInvoker.OnPostArgumentLoad []
cli.knack.cli: Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument..add_ids_arguments at 0x00000237995B1440>, <function register_cache_arguments..add_cache_arguments at 0x00000237995B1580>]
cli.knack.cli: Event: CommandInvoker.OnCommandTableLoaded []
cli.knack.cli: Event: CommandInvoker.OnPreParseArgs []
cli.knack.cli: Event: CommandInvoker.OnPostParseArgs [<function OutputProducer.handle_output_argument at 0x00000237966D6200>, <function CLIQuery.handle_query_parameter at 0x0000023796703D80>, <function register_ids_argument..parse_ids_arguments at 0x00000237995B14E0>]
urllib3.connectionpool: Starting new HTTPS connection (1): aka.ms:443
urllib3.connectionpool: https://aka.ms:443 "GET /BicepLatestRelease HTTP/1.1" 301 0
urllib3.connectionpool: Starting new HTTPS connection (1): downloads.bicep.azure.com:443
urllib3.connectionpool: https://downloads.bicep.azure.com:443 "GET /releases/latest HTTP/1.1" 200 39220
cli.knack.cli: Event: CommandInvoker.OnTransformResult [<function _resource_group_transform at 0x0000023799592520>, <function x509_from_base64_to_hex_transform at 0x00000237995925C0>]
cli.knack.cli: Event: CommandInvoker.OnFilterResult []
cli.knack.cli: Event: Cli.SuccessfulExecute []
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x0000023799557100>]
az_command_data_logger: exit code: 0
cli.main: Command ran in 1.201 seconds (init: 0.185, invoke: 1.016)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 3486 in cache
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\azure\cli\telemetry_init.pyc .azure"
telemetry.process: Return from creating process
telemetry.main: Finish creating telemetry upload process.

Expected behavior

az bicep upgrade should install the latest version if it is advertising a new version.

Environment Summary

azure-cli 2.58.0

core 2.58.0
telemetry 1.1.0

Extensions:
containerapp 0.3.49
cosmosdb-preview 0.26.0
front-door 1.0.17
serviceconnector-passwordless 0.3.13
storage-preview 1.0.0b1
storagesync 1.0.0

Dependencies:
msal 1.26.0
azure-mgmt-resource 23.1.0b2

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users<snip>.azure\cliextensions'

Python (Windows) 3.11.7 (tags/v3.11.7:fa7a6f2, Dec 4 2023, 19:24:49) [MSC v.1937 64 bit (AMD64)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Additional context

No response

[yonzhan]

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

[torreymicrosoft]

Thanks for your patience, @onionhammer — this was recently picked up as an outstanding open issue for the ARM Deployments team to review.

There's been some movement here. On current CLI (2.85.0), az bicep upgrade no longer goes completely silent — when you're already current it prints a status line, e.g.:

Bicep CLI 0.43.8 is already installed at '<path>'.

What I can't reproduce from here is the specific branch you hit — "a newer version is advertised, but az bicep upgrade is a no-op" — because this machine is already on the latest Bicep. Could you az upgrade and, next time az bicep version advertises a newer release, run az bicep upgrade and let us know whether it (a) actually installs the new version and (b) prints a clear message? If it still silently no-ops on an available upgrade, the output of az bicep upgrade --debug at that moment would let us pin it down.

Closing this issue as couldn't repro. Thanks!

[onionhammer]

@torreymicrosoft it only happens around the time when a new version is released - is that when you're testing it?

[torreymicrosoft]

@onionhammer Ah I didn't catch that. No - let me test it during explicitly when a new version is released and get back to you.