AzureDeploymentFramework
azure-quickstart-templates
| AzureDeploymentFramework | azure-quickstart-templates | |
|---|---|---|
| 1 | 42 | |
| 144 | 13,724 | |
| - | 0.5% | |
| 8.8 | 9.9 | |
| 4 months ago | 5 days 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.
AzureDeploymentFramework
-
Devops Pipeline + Bicep - Advice on how to structure
This is a great resource on how to structure bicep modules https://github.com/brwilkinson/AzureDeploymentFramework/tree/main/ADF/bicep we do something similar and provide a parameter file per region calling the main.bicep file twice.
azure-quickstart-templates
- Instantly Deploy BrowserBox on Azure Cloud – open-source isolated browser
- Deploy BrowserBox from an Azure Quickstart Template
- Chef extension for Azure VM
-
Chef extension for Azure VM in Bicep
I found a quick start template for this in Arm, I’m sure if you just decompile the ARM json it will give you a good heads start on how it should work.
-
Bicep: Cyclical Dependency Issue (Network resources)
There is a GitHub issue regarding this topic - https://github.com/Azure/azure-quickstart-templates/issues/2786
- Struggling to understand "_artifactsLocation" parameter when using ARM templates
-
Removing secondary disk
I'm using this video (https://www.youtube.com/watch?v=J4NCvIMuzVE) as a guide to start building out Windows VM's, and running into some questions. I'm trying to use the template located here ( azure-quickstart-templates/quickstarts/microsoft.compute/vm-simple-windows at master · Azure/azure-quickstart-templates (github.com)).
- The yaml document from hell
-
ARM / Bicep template development just by hand?
You can use quick start templates (https://github.com/Azure/azure-quickstart-templates/) as a starting point, but not all examples are bicep ready yet. But those can be easily converted to bicep.
-
SFTP for Azure Blob Storage Generally Available - Pricing
I think it was this one https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files-existing-storage and this https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files
What are some alternatives?
CanadaPubSecALZ - This reference implementation is based on Cloud Adoption Framework for Azure and provides an opinionated implementation that enables ITSG-33 regulatory compliance by using NIST SP 800-53 Rev. 4 and Canada Federal PBMM Regulatory Compliance Policy Sets.
bicep - Bicep is a declarative language for describing and deploying Azure resources
PSBicep - This is the repo for the Bicep PowerShell Module.
photoprism-auto-index - Photoprism supercharged with originals folder auto indexing
azure-tailscale-aci-deploy - ARM & Bicep Templates to deploy a Tailscale subnet router with ACI
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
TheYAMLPipelineOne - Azure DevOps YAML Templates
f5-azure-arm-templates - Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure
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.
protonmail-bridge-docker - ProtonMail IMAP/SMTP Bridge Docker container
opnazure - This template allows you to deploy an OPNsense Firewall Azure VM using the opnsense-bootsrtap installation method