This repository includes a CI platform for and collection of curated DEMO Bicep modules. The platform supports both ARM and Bicep and can be leveraged using GitHub actions as well as Azure DevOps pipelines.
Above diagram outlines the high-level overview of how the structure outlined in this repository is aiming to be consumed.
- Cloud Engineering Team - Team dedicated to maintaining the repository, and providing training to the consuming parties to properly leverage this structure.
- Centrally Managed Modules Repository - this repository, contains the Bicep module and pipeline definitions, as well as the relevant documentation to ensure all consuming parties are made aware of new releases and standards, and how to introduce new changes through a workflow such as GitHub issues.
- Azure Container Registry - This sturcture relies on Azure Container Registry (ACR) as its private-registry, but this component can be replaced with any other private-registry that supports universal packages.
- Users - Consuming parties that will rely on the centralized private registry to pull in pre-defined templates to deploy their infrastructure as code.
| Name | Status |
|---|---|
| Key Vaults |  |
| Network Security Groups |  |
| Resource Groups |  |
| Resources Tags |  |
| Role Assignments |  |
| Role Definitions |  |
| Storage Accounts |  |
| Virtual Networks |  |
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 opencode@microsoft.com 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.