Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
az bicep version check should not block on failure
See original GitHub issueRelated command
az bicep *
az deployment * (with a bicep template file)
Is your feature request related to a problem? Please describe.
the az commands that use bicep, check for a newer version of bicep before initiating the command. If that version check fails for some reason (e.g. 4xx) the command stops and the user is blocked from using any command that involves bicep in the cli
Describe the solution you’d like ignore failures that occur during the bicep version check and continue running the user’s command
Describe alternatives you’ve considered the user can modify the json file that has a timestamp for a version check to a future date and that will unblock, but for users running pipelines this is not always trivial.
Additional context We are working on changes that will make the check more resilient, but even with that – in the event of a failure, we should not block the user’s command.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@shenglol
@shenglol is probably a better person to have a look…