Bicep is a new template language which is used to create the ARM template. You can either write ARM JSON from scratch or use Bicep language to create the ARM template. Bicep is a domain-specific language(DSL) that uses declarative syntax to deploy Azure resources.
You can read more about Bicep here.
If you have provisioned JSON templates before, You'll know it is non-trivial to write them so Bicep is a step to make it easier.
Bicep project is maintained at Github
This workshop will help you to understand & implement the templates in Bicep. You will go through multiple challenges and after completing the challenges you should have a working knowledge of Bicep.
You need to setup your machine before you should run the challenges.
- Visual studio code
- You can download the VS code from here
- Visual Studio code Bicep extension
- Install the VS code extension from here
- CLI setup
- Please refer this link to install & run Bicep. You can use either Azure CLI or Powershell.
Once you have setup your environment, You can start the bicep workshop challenges.
- Team Working Agreement
- Team Engineering Practices
- CSE Engineering Fundamentals Playbook
This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
For help and questions about using this project, please open a GitHub issue.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services.
Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines.
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party's policies.