Book Image

Terraform Cookbook

By : Mikael Krief
Book Image

Terraform Cookbook

By: Mikael Krief

Overview of this book

HashiCorp Configuration Language (HCL) has changed how we define and provision a data center infrastructure with the launch of Terraform—one of the most popular and powerful products for building Infrastructure as Code. This practical guide will show you how to leverage HashiCorp's Terraform tool to manage a complex infrastructure with ease. Starting with recipes for setting up the environment, this book will gradually guide you in configuring, provisioning, collaborating, and building a multi-environment architecture. Unlike other books, you’ll also be able to explore recipes with real-world examples to provision your Azure infrastructure with Terraform. Once you’ve covered topics such as Azure Template, Azure CLI, Terraform configuration, and Terragrunt, you’ll delve into manual and automated testing with Terraform configurations. The next set of chapters will show you how to manage a balanced and efficient infrastructure and create reusable infrastructure with Terraform modules. Finally, you’ll explore the latest DevOps trends such as continuous integration and continuous delivery (CI/CD) and zero-downtime deployments. By the end of this book, you’ll have developed the skills you need to get the most value out of Terraform and manage your infrastructure effectively.
Table of Contents (10 chapters)

Testing the compliance of Terraform configurations using Sentinel

The aspect of Terraform configuration tests has been discussed several times in this book, such as using terratest (in the Testing Terraform module code with Terratest recipe of Chapter 5, Provisioning Azure Infrastructure with Terraform) and kitchen-terraform (in the Testing Terraform configuration using kitchen-terraform recipe of Chapter 7, Deep Diving into Terraform). The common point of these two tools is that the purpose of the tests is to write and test the changes that have already been applied by Terraform.

All these tests are very beneficial but they are done after the changes have been made. The rollback also requires work from all teams. To be even more in line with the business and financial requirements of the company, there is another level of testing that verifies the compliance of the Terraform configuration before it is applied to the target infrastructure.

In Terraform, these compliance tests are carried...