Azure
`bicep build`/`bicep decompile` service
In order to support both Portal template export and portal deployment with bicep files, we need to stand up APIs for sending bicep code and returning the generated template and vice-versa.
Related to #2369
For export as Bicep in the portal, we would need to decompile a single template into a single Bicep file, which should be fairly easy to model in an API. Having a single-file compile API is also easy to model.
We will need to decide whether we should support multiple files with this API. For example, would we need to support compiling a file referencing local modules? Would the API also need to handle any private registries once they're available?
Additionally to the API service it would be useful to have other tools to compile into arm. For go/python developers like us, msbuild or cli commands are not really feasible to process the bicep files. At the end of the day we need to send the json templates to Azure RM and we need a way to programmatically compile with go or python.
The referenced sample I had to compile a JSON template so users could easily deploy it. While not a big issue, Bicep templates seem a lot easier to read for the purposes of samples, which pair nicely with using the typical Deploy to Azure buttons.
