Deploy to Azure Button with Bicep
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 81
Description
We built an MVP for this at our most recent Hackathon which can be seen here: https://garagehackbox.azurewebsites.net/hackathons/2356/projects/106074
However, there are still some important missing pieces for this to be declared production-ready, so please treat this as experimental:
• Support for modules (module files & the module registry)
• Support for bicepconfig.json
• Support for multiple versions of Bicep
• Migrating the service to a production subscription (and associated actions such as setting up monitoring)
Let us know if you are interested and we can try to prioritize it accordingly.
Contributor guide
Research direction
Start by reviewing the linked hackathon MVP for the Deploy to Azure button and compare it with the listed production gaps. Done means supporting modules and the module registry, bicepconfig.json, multiple Bicep versions, and migration to a production subscription with associated monitoring actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100