ResourceModules
opnazure
Our great sponsors
| ResourceModules | opnazure | |
|---|---|---|
| 12 | 2 | |
| 716 | 144 | |
| 0.8% | - | |
| 9.6 | 7.2 | |
| 19 days ago | 5 months ago | |
| Bicep | 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.
ResourceModules
-
How do you design IaC modules and automations?
That is a great question, and not the least because it's the one I've been struggling with for the past few years. As for Azure and Bicep, we tried out a few things until we found out about the Common Azure Resource Modules Library (https://github.com/Azure/ResourceModules) and started experimenting on how to leverage that. Wheter you find such modules useful or not, I would suggest taking a look at the module design principles they have (https://github.com/Azure/ResourceModules/wiki/The%20context%20-%20CARML%20library), which I've found to be great.
- How does Microsoft update the README.md of a specific module in GitHub?
- In GitHub, how does Microsoft automatically update the README.md of a respective module?
- How does Microsoft update their README.md
-
How are you splitting out your IaC pipelines?
In general resource group is lifecycle and deployment boundary. So your Bicep or ARM templates should deploy resource groups with all resources included. To make it easier you can use resource modules from https://github.com/Azure/ResourceModules.
- Anyone using ACR Repository for Bicep Modules with ADO?
-
Devops Pipeline + Bicep - Advice on how to structure
For modularized Bicep, I'd suggest you to take a look at Common Azure Resource Modules Library - probably not much of an use right now if you have implemented everything, but could be of use if you feel like refactoring something. I wouldn't suggest it as an example on how to do custom bicep implementation, but one can certainly take some inspiration from there, if not directly using the modules.
-
ARM / Bicep template development just by hand?
What I found is that using the Resource Modules (https://github.com/Azure/ResourceModules) repo is the best approach. It simplifies the authoring quite a lot in my opinion. And every module on the repo is bicep. But since the modules are created by Microsoft/the community, not every resource or service has a ready module. I have been using it for the last 6-8 months, and find it covers 90% of my scenarios. And each module is quite well documented, but in some cases you have to study the module to figure out the required inputs.
-
How to structure code repositories
We don't have a team in place to update and maintain modules so that's where my thought about CARML comes into the picture. Unsure how this is maintained though and how to update the modules, and i think it makes it more complex and hard to understand for people unfamiliar with IaC.
- Bicep templates
opnazure
- S2S VPN for Test Lab
-
Free (Community) edition of pfSense on Azure - weird pricing?
This template could be a good option if you wanna use OPNsense instead of pfSense. Perfect for production environment, https://github.com/dmauser/opnazure
What are some alternatives?
avdaccelerator - AVD Accelerator deployment automation to simplify the setup of AVD (Azure Virtual Desktop) based on best practices
azure-quickstart-templates - Azure Quickstart Templates
PSBicep - This is the repo for the Bicep PowerShell Module.
Enterprise-Scale - The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
PSDocs - Generate documentation from Infrastructure as Code (IaC).
ALZ-Bicep - This repository contains the Azure Landing Zones (ALZ) Bicep modules that help deliver and deploy the Azure Landing Zone conceptual architecture in a modular approach. https://aka.ms/alz/docs
data-management-zone - Template to deploy the Data Management Zone of Cloud Scale Analytics (former Enterprise-Scale Analytics). The Data Management Zone provides data governance and management capabilities for the data platform of an organization.
aks-baseline - This is the Azure Kubernetes Service (AKS) Baseline Cluster reference implementation as produced by the Microsoft Azure Architecture Center.
bicep-registry-modules - Bicep registry modules
AzureDeploymentFramework - ARM Bicep & DSC Project for Azure Infrastructure and App Environment Deployments.
hub-and-spoke-playground - A collection of BICEP/ARM templates that deploys on Azure a hub & spoke net topology aligned with Microsoft Enterprise scale landing zone ref architecture to use as playground for test and study. As bonus many scenarios with step-by-step solutions for studying and learning are also available
Azure-IAC-Bicep - An IAC Management for Azure using Bicep