PSBicep
bicep-registry-modules
Our great sponsors
| PSBicep | bicep-registry-modules | |
|---|---|---|
| 1 | 4 | |
| 129 | 358 | |
| 3.1% | 13.7% | |
| 7.7 | 9.8 | |
| about 2 months ago | about 18 hours ago | |
| PowerShell | Bicep | |
| 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.
PSBicep
-
Anyone using ACR Repository for Bicep Modules with ADO?
Currently the automated testing we have in the pipeline is only building the bicep into ARM, and running psrule against the biceps (which, I think, is essentially the same thing). We used to run the Test-command of PSBicep-module (https://github.com/PSBicep/PSBicep/blob/main/Docs/Help/Test-BicepFile.md), but ran into problems with that one, as the module tends to lack behind latest bicep features a bit - same thing with a lot of tooling like psrule.
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?
What are some alternatives?
PSRule.Rules.Azure - Rules to validate Azure resources and infrastructure as code (IaC) using PSRule.
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.
AzureDeploymentFramework - ARM Bicep & DSC Project for Azure Infrastructure and App Environment Deployments.
azure-quickstart-templates - Azure Quickstart Templates
PSDocs - Generate documentation from Infrastructure as Code (IaC).
PSRule - Validate infrastructure as code (IaC) and objects using PowerShell rules.
AzDocs
AzOps - AzOps is a PowerShell module which deploys (Push) ARM Resource Templates & Bicep files at all Azure scope levels and exports (Pull) ARM resource hierarchy.
PSRule.Rules.AzureDevOps - PSRule Module for Azure DevOps. Audit your Azure DevOps project configuration for best practice adoption in minutes.