Restoring modules is slow and could be parallelized
Open
Needs: Upvote
story: registry
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
We would also consider adding the ability to retry/force a specific module or maybe all modules that failed.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the module restoration flow, then determine how parallel restoration and retrying or forcing failed modules should behave; done means the intended behavior is implemented and verified for the relevant restoration cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100