`bicep build` service
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
For portal deployment with bicep files, we need to stand up APIs for sending bicep code and returning the generated template.
Opening this issue specifically for the build service, as the decompile service is being delivered, this issue builds on https://github.com/Azure/bicep/issues/3003
Now that `decompile` is being completed, what scenarios need `build` support?
Contributor guide
Research direction
Start by reading the linked issue 3003 and the decompile-service work referenced in this issue, then review the portal deployment scenario. The work is complete when the required build scenarios are agreed and the API requirements for accepting Bicep code and returning the generated template are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100