Azure DevOps Infrastructure Automation with Terraform and GitHub Actions

Author: Regis Nde Tene (Chopinregis)

Status: Draft

Duration: 1 Week Deep Dive

Executive Summary

This project focuses on automating the deployment of a multi-tier web application infrastructure on Azure using Terraform for Infrastructure-as-Code and GitHub Actions for CI/CD. It involves scripting, Azure networking configuration, and cloud automation to provision and manage resources, as well as implementing monitoring and troubleshooting capabilities for ensuring environment stability.

Key Skills

Project Execution Log

Stage 1: Design Azure Infrastructure and Networking

In this stage, we successfully designed the Azure infrastructure for a multi-tier web application, focusing on service selection, network segmentation, and security. We mapped application requirements to specific Azure services, defined a secure VNet topology with dedicated subnets and detailed NSG rules, and documented the entire design for future implementation. This foundational design ensures a secure, scalable, and efficient environment before any code is written.

Deliverables

  • [x] Azure Infrastructure Design Document (Markdown or PDF)
  • [x] Detailed Azure Network Topology Diagram (e.g., draw.io, Visio)
  • [x] Azure Resource List with Specifications and Naming Conventions

Stage 2: Develop Terraform Modules for Core Resources

This stage successfully laid the groundwork for our Azure infrastructure automation by developing core Terraform modules. We learned how to encapsulate resource definitions, manage input variables, and expose output values for `Resource Groups`, `Virtual Networks`, and `Storage Accounts`. This modular approach significantly improves the reusability, maintainability, and scalability of our infrastructure-as-code efforts, ensuring a robust foundation for future deployments.

Deliverables

  • [x] Terraform module directory for Azure Resource Groups (e.g., `modules/resource-group`), including `main.tf`, `variables.tf`, and `outputs.tf`.
  • [x] Terraform module directory for Azure Virtual Networks (e.g., `modules/vnet`), including subnets, containing `main.tf`, `variables.tf`, and `outputs.tf`.
  • [x] Terraform module directory for Azure Storage Accounts (e.g., `modules/storage-account`), including `main.tf`, `variables.tf`, and `outputs.tf`.
  • [x] Root Terraform configuration file (e.g., `environments/dev/main.tf`) demonstrating the successful instantiation and interconnection of the created core modules.

Stage 3: Implement CI/CD Pipeline with GitHub Actions

This stage focused on automating the Terraform-based infrastructure deployment using GitHub Actions. We learned how to create an Azure Service Principal for secure authentication, configure GitHub repository secrets to store credentials, and define a comprehensive GitHub Actions workflow that performs `terraform init`, `validate`, `plan`, and `apply` operations. This establishes a robust CI/CD pipeline, significantly improving the efficiency and reliability of infrastructure management.

Deliverables

  • [x] A working `azure-terraform-ci.yml` (or similar) GitHub Actions workflow file, committed to the repository.
  • [x] A successfully executed GitHub Actions pipeline run log, demonstrating `terraform plan` and `terraform apply` completion for a small change.
  • [x] Updated Azure infrastructure reflecting changes pushed through the CI/CD pipeline.
  • [x] Brief documentation detailing how to trigger the pipeline, how to review logs, and steps for basic troubleshooting or manual intervention.

Stage 4: Script Deployment Automation and Configuration

This stage focused on developing and implementing automation scripts for application deployment and configuration tasks. We learned to identify manual processes, choose appropriate scripting languages, parameterize scripts for environmental flexibility, and integrate with Azure Key Vault for secure secret management. The outcome is a set of reliable, version-controlled scripts that significantly enhance deployment efficiency and security, preparing the groundwork for CI/CD integration.

Deliverables

  • [x] `deployment_scripts/` folder containing parameterized Python or PowerShell scripts for application deployment and configuration.
  • [x] `config/` folder with environment-specific configuration files (e.g., `dev.json`, `prod.json`) or variable definitions for script input.
  • [x] A successfully deployed and configured sample application instance on the Azure infrastructure.
  • [x] `scripts_documentation.md`: Markdown document detailing script usage, parameters, and common troubleshooting steps.

Stage 5: Deploy Infrastructure and Application

This stage successfully deployed the entire multi-tier web application infrastructure and the application itself onto Azure. By leveraging `Terraform` for infrastructure provisioning and `GitHub Actions` for CI/CD, the deployment was automated, repeatable, and verifiable. This involved careful planning, execution, and validation to ensure all components were correctly provisioned and functional, marking a critical milestone in bringing the application to life in the cloud.

Deliverables

  • [x] `Terraform` state file (`terraform.tfstate`) stored in the configured remote backend (e.g., Azure Storage Account), reflecting the successfully deployed infrastructure.
  • [x] A comprehensive log of the successful `GitHub Actions` workflow run, detailing both the `Terraform` infrastructure provisioning and the application deployment steps.
  • [x] The public URL of the deployed multi-tier web application, accompanied by a screenshot or confirmation of its successful loading and basic functionality.
  • [x] A list of key Azure resources deployed, verifiable via Azure portal or `Azure CLI` commands (e.g., `az group show --name <resource-group-name>`).

Stage 6: Monitor and Troubleshoot Environment

In this stage, we successfully implemented a robust monitoring and alerting framework for the Azure infrastructure. We leveraged Azure Monitor, Log Analytics, and Application Insights to centralize data, visualize performance, and configure proactive alerts. Furthermore, we gained practical experience in troubleshooting common issues and developed essential runbooks, significantly enhancing the environment's reliability and our ability to respond to incidents.

Deliverables

  • [x] Monitoring Configuration Scripts/Templates: `Terraform` configuration files or `Azure Bicep` templates defining diagnostic settings, Log Analytics workspace, Application Insights resources, and alert rules.
  • [x] Azure Monitor Dashboard Link: A URL to the fully configured Azure Monitor dashboard providing an overview of the environment's health.
  • [x] Alert Rules Configuration Report: A document or exported list detailing all configured alert rules, their thresholds, action groups, and notification methods.
  • [x] Basic Troubleshooting Guide: A markdown document outlining common issues, their symptoms, and initial steps for diagnosis and resolution.