Better Error Handling when Bicep installation fails
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, github-actions, typescript
Research direction
Start with the Bicep installation step used by Azure/bicep-deploy@v2 and reproduce the intermittent download failure described in the issue. Investigate how repeated steps currently download Bicep and create temporary directories. Done means failed downloads are retried, an existing worker installation can be used, and repeated deployment steps avoid unnecessary downloads.
Written by the indexing model from the issue text.
Description
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?
- Maybe don't randomly generate a dir each time, like
- Dominant language
- TypeScript
- Stars
- 66
- Forks
- 20
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 22
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/bicep-deploy
-
Bicep Deploy task masks RestError when `details` is undefinedPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Azure/bicep-deploy#350 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/bicep-deploy#309 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/bicep-deploy#347 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Azure/bicep-deploy#328 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Azure/bicep-deploy#322 ·
Maintainers usually reply within 1 day
All issues in Azure/bicep-deploy
Similar issues
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
umami-software/umami#4686 · 1 comment ·
Maintainers usually reply within 2 days
-
[Bug]: Device screenshot fails with 500 on iPhone Duo (Xcode 27.2): serve-sim calls simctl without --displayPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
pingdotgg/t3code#24900 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inu-appcenter/UNIDorm-web#411 ·
Maintainers usually reply within 1 day
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days