create-infra-pipeline

To set up an Azure DevOps pipeline for Terraform, you need a YAML configuration with separate plan and apply stages. This generates standardized pipelines where the plan stage always runs and publishes artifacts, while the apply stage is restricted to protected branches with mandatory approval gates.

Yes, you can automate Terragrunt CI/CD pipelines in Azure DevOps by generating YAML configurations that include a 20-minute lock timeout convention. This ensures consistent deployment workflows across multiple Terragrunt components without manually writing pipeline code for each one.

Infrastructure drift detection identifies unplanned changes in your infrastructure by running scheduled Terraform plan checks on a regular cadence. In a CI/CD pipeline, this is configured as a scheduled job that compares your actual cloud state against your infrastructure-as-code configuration.

Yes, the generated pipeline setup supports Azure authentication for Terraform using secure Azure Managed Service Identity. This integrates directly into the pipeline YAML to authenticate Terraform and Terragrunt deployments without storing manual credentials.

To add approval gates to protected branches in Azure DevOps YAML, configure the apply stage with branch restrictions and mandatory approvals. This ensures infrastructure changes cannot be applied without manual review on designated protected branches.

The best way to standardize Terraform pipelines across multiple environments is to use shared template repositories that generate consistent YAML configurations. This approach applies uniform plan and apply stages, drift detection schedules, and authentication methods across all infrastructure components.