Better Error Handling when Bicep installation fails

[o-l-a-v]

Using Azure/bicep-deploy@v2 (thus v2.2.0) on a public GitHub worker failed and crashed the workflow with the foloowing as the only error output:

Error: request to https://downloads.bicep.azure.com/releases/latest failed, reason: 

I re-ran all jobs and it worked again.

Requests:

• Make this step more resilient.
  • Try multiple times.
  • Fall back to Bicep installed on the worker if present.
• Don't download Bicep on each step? If running multiple bicep-deploy steps, like validate and then what-if, the actions seems to download Bicep each time.
  • Maybe don't randomly generate a dir each time, like Installed Bicep version 0.35.1 to /tmp/bicep-6j9Ypj/bicep.
  • Or cache the downloaded file?

[mblaschke-daimlertruck]

also happend here multiple times, bicep-deploy action is not stable at all because the download failed.

But we have the latest bicep binary installed in our cicd agents, we also would like to skip the installation at all.

workaround: do not use this action and deploy via powershell/az cli task.