Native "Deploy to Azure" support for bicep files
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
Currently, we can deploy templates defined in JSON straight from Github like so:
`[](https://portal.azure.com/#create/Microsoft.Template/uri/encoded-url-to-template.json)|`
### Example
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmatthiasguentert%2Fazure-naming-convention-initiative%2Fmain%2Fdist%2Fnaming-convention-mg.json)|
It would be great to see bicep support for this so we can use it accordingly
`[](https://portal.azure.com/#create/Microsoft.Template/uri/encoded-url-to-template.bicep)|`
Contributor guide
Research direction
Start by reviewing the issue's existing Deploy to Azure URL example and the Azure Portal template deployment entry point. Define how a .bicep URL should be handled alongside the shown .json flow, then verify that the resulting button can deploy the referenced Bicep file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100