Bicep Modules
Summary
The following table shows the number of all available, orphaned and planned Bicep Modules.
| Language | Classification | Published 🟢 & 🟡 | Proposed ⚪ | SUM |
|---|---|---|---|---|
| Bicep | Resource | 167 | 19 | 186 |
| Pattern | 41 | 30 | 71 | |
| Utility | 1 | 1 | 2 |
Want to contribute to AVM Bicep modules?
| # | Labels | Link and description |
|---|---|---|
| 1. | Type: New Module Proposal 💡 Needs: Module Owner 📣 Language: Bicep 💪 | To become the owner of a new Bicep module, see all new Bicep modules looking for owners or check out the “Looking for owners” swimlane here. |
| 2. | Status: Module Orphaned 🟡 Language: Bicep 💪 | To become the owner of an orphaned Bicep module, see all orphaned Bicep modules or check out the “Orphaned” swimlane here. |
| 3. | Needs: Module Contributor 📣 Language: Bicep 💪 | To become a co-owner or contribute to a Bicep module, see all Bicep modules looking for contributors. |
For more details on “What are the different ways to contribute to AVM?”, see here.
Status Badges
This section gives you an overview of the latest workflow status of each AVM module in the Public Bicep Registry repository.
Note
While some pipelines can momentarily show as red, a new module version cannot be published without a successful test run. A failing test may indicate a recent change to the platform that is causing a break in the module or any intermittent errors, such as a periodic test deployment attempting to create a resource with a name already taken in another Azure region.
