bicep-registry-modules
PSDocs
Our great sponsors
bicep-registry-modules | PSDocs | |
---|---|---|
4 | 1 | |
355 | 133 | |
13.0% | 0.8% | |
9.8 | 4.6 | |
7 days ago | 2 months ago | |
Bicep | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bicep-registry-modules
-
Anyone using ACR Repository for Bicep Modules with ADO?
We have a separate parameter file for every landing zone instance (our implementation is a bare-bones CAF landing zone, kinda like https://github.com/Azure/bicep-registry-modules/tree/main/modules/lz/sub-vending, which is avaible from bicep public registry), where instance is for example a separate environment (dev/test/prod). This parameter file only represents the configuration, so things like subnets, nsgs and so on, and it has nothing to do with the landing zone implementation as such.
-
ARM / Bicep template development just by hand?
As you point out, it is another layer of abstraction that can make it more complex. Specifically it will add a pain point with the replication of the modules from /ResourceModules to the private repo. (I dont have a good solution for that at the moment) Microsoft has a public container registry (https://github.com/Azure/bicep-registry-modules) that someday may be updated to contain everything in /ResourceModules
-
Bicep templates
Still a work in progress, but the official bicep registry - https://github.com/Azure/bicep-registry-modules
- Anyone know if it is doable to rewrite this github workflow to ado pipeline?
PSDocs
-
Anyone using ACR Repository for Bicep Modules with ADO?
For Pull Requests, it compiles bicep into ARM templates and runs PSDocs for them an accompaying json file that holds versioning information and, document title and some additional information. Then it looks for ./test/module.test.bicep -file (which is just a copy of a suitable test suite from ResourceModules) and runs psrule against that. For runs triggered from main-branch, it queues the module publishing pipeline for every changed module.bicep found.
What are some alternatives?
PSBicep - This is the repo for the Bicep PowerShell Module.
ResourceModules - This repository includes a CI platform for and collection of mature and curated Bicep modules. The platform supports both ARM and Bicep and can be leveraged using GitHub actions as well as Azure DevOps pipelines.
azure-quickstart-templates - Azure Quickstart Templates
PSRule - Validate infrastructure as code (IaC) and objects using PowerShell rules.
SharePointDsc - The SharePointDsc PowerShell module provides DSC resources that can be used to deploy and manage a SharePoint farm
AzDocs
getSAMLResponse-Interactive - Set of tools to interactively authenticate to a SAML IDP and return SAML Response.
PSRule.Rules.Azure - Rules to validate Azure resources and infrastructure as code (IaC) using PSRule.