How mofaizal/fun-project-playground works
Main Components
• AVM Core Modules: These are the reusable, parameterized module definitions (e.g., “alz” directory and its archetype definitions) that represent core building blocks of Azure landing zones.
• Infrastructure Examples: Each of the directories named “avm-<...>” (for example, avm-workload, avm-vnet-lb-vmss, avm-secure-hub, etc.) represents one example deployment and should be considered as an independent sub-system.
• Network Components: Within these examples, identify key infrastructure elements such as Virtual Networks (VNETs), Subnets, Network Security Groups (NSGs), and connection components (e.g., VPN setups, peering).
• Compute and Application Layers: Examples using VM Scale Sets, application gateways, load balancers, and application workload deployments.
• Support Files: Files like variables.tf, terraform.tfvars.sample, and main.tf indicate configuration points and parameter sets that guide the module behavior.
Relationships and Interactions
• Directional data flow from input parameters (defined in terraform.tfvars or settings files) into the module configurations that then deploy Azure resources.
Architectural Patterns and Design Principles
• Modularity: Emphasize how the repository separates concerns by having a central library of AVM modules (the “alz” directory and its archetypes) and a collection of example deployments in different directories.
• Parameterization & Reusability: Note the use of variable files and environment-specific settings (e.g., separate tf files for dev, non-prod, prod) which underpin the design.
• Layered Architecture: Indicate distinct layers such as the networking layer (VNETs, subnets, NSGs), the compute/application layer (VMSS, app gateway), and potentially the security layer (secure hub modules) that interact to build comprehensive environments.
Relevant Technologies
• Terraform – Used for infrastructure-as-code deployments.
• Azure Verified Modules – Acting as the reference implementation for deploying Azure networks, compute resources, and more.
• YAML and JSON configurations – For module definitions and custom extensions.
• Shell Scripts – As seen in the app gateway SSL certificate generation scripts, which show operational execution steps in the modules.