Timing of bicep upgrade message
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
When I run `az deployment group create` I often get a message like `A new Bicep release is available: v0.5.6. Upgrade now by running "az bicep upgrade".`
It always annoys me because I cannot run the suggested upgrade while the terminal is blocked waiting for the deployment. I haven't tried to open another terminal to run the upgrade in parallel, because I am not sure if it is safe to do so.
When the deployment finishes, I have forgotten about the update, and the upgrade message gets scrolled out of view by the deployment success/error message. So I forget to upgrade and receive the same upgrade warning message again and again.
I would suggest to move the message so it appears on screen below the deployment success/error message and appears just when the command completes.
Contributor guide
Research direction
The entry points named are `az deployment group create` and `az bicep upgrade`; start by tracing where the Bicep upgrade notice is emitted during deployment. Verify the notice appears after the deployment success or error output and that the existing upgrade command remains actionable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100