How blastik/opella-devops-challenge works
Project type and purpose
• This is an Infrastructure-as-Code (IaC) DevOps project whose goal is to provision and manage Azure infrastructure using Terraform.
• Key deliverables:
• A reusable Terraform module to deploy an Azure Virtual Network (VNET)
• Environment-specific Terraform configurations (e.g., dev, prod) that consume that module
• A GitHub Actions pipeline to plan and apply changes
(expected) file structure
Although the provided file tree only contains README.md, the README implies a structure like:
├─ modules/
│ └─ vnet/ ← reusable VNET module (main.tf, variables.tf, outputs.tf, tests/)
├─ envs/
│ ├─ dev/ ← dev.tf, provider.tf, backend.tf, variables.tf
│ └─ prod/ ← prod.tf, provider.tf, backend.tf, variables.tf
└─ .github/workflows/
└─ ci.yml ← Terraform plan & apply pipeline
Extract architecture insights from the README
• Reusable, parameterized module for VNET deployment
• Multiple environments handled via separate folders or workspaces
• GitHub pipeline orchestrating Terraform lifecycle
• Use of Azure resource groups, virtual machines, blob storage, etc.
Main components
a. Developer & GitHub repository
b. CI/CD platform: GitHub Actions workflows
c. Terraform code:
• modules/vnet (reusable)
• envs/{dev,prod} (environment configs)
• Terraform state backend (e.g., Azure Storage Account)
d. Azure infrastructure:
• Resource Groups (dev-rg, prod-rg)
• Virtual Network + subnets (from vnet module)
• Virtual Machines (in dev/prod)
• Blob Storage or other chosen resources
e. External services as needed (e.g., Azure Active Directory for authentication)
Relationships and data flows
• Developer pushes code → GitHub repo
• GitHub Actions trigger → runs Terraform init/plan/apply
• Terraform module is invoked by env configs → provisions resources into Azure
• Terraform state is stored in remote backend (Azure Storage)
• Outputs (e.g., subnet IDs, VM public IPs) are displayed in pipeline logs
Architectural patterns and design principles
• Modular design: separate reusable module(s) from environment-specific code
• Environment isolation: separate state files and resource groups per environment
• CI/CD as code: pipeline defined alongside Terraform code
• Security & maintainability: parameterization of sensitive values, tagging, automated testing (if any)
Relevant technologies and frameworks
• Terraform core (HCL)
• GitHub Actions (YAML pipelines)
• Azure Provider for Terraform
• Azure Resource Manager (ARM) resources
• (Optional) Terraform testing tools (e.g., terratest)
Detail
• Every major Terraform file grouping (modules, envs, backends)
• Remote state backend and locking mechanism
• Optional test harness if implemented
• Tagging/labeling strategy in notes or callouts