Terraform

Overview

We use Terraform where the estate is not only Azure, or where your platform team already standardises on it. State is stored remotely with locking, the AzureRM provider is pinned, and modules match the resources this engagement will own.

We plan in a pipeline, apply only from that pipeline, and document imports for resources that already exist. A change that would replace a database or a storage account is called out before apply, not discovered in the log.

What we deliver

• Terraform modules and environment stacks for the agreed resources
• Remote state with locking and a pinned AzureRM provider
• Pipeline plan and apply, with production apply protected
• Import or a rebuild plan for resources that already exist

Business benefits

• Azure changes follow the same tool as the rest of the estate
• State locking stops two applies from writing at once
• A plan shows replacement of data resources before anyone applies it