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)

Automating Terraform Cloud using APIs

In the previous recipes, we learned how to use the Terraform Cloud platform to store Terraform state files in a remote backend. Then, we used Terraform Cloud as a private registry of modules and learned how to run Terraform configurations remotely in Terraform Cloud.

All these actions were mainly done via the Terraform Cloud UI web interface. In the There's more... section of the previous recipe, we discussed that it is also possible to use the Terraform CLI locally to run Terraform remotely.

In a company, we need to automate all of these actions for the following reasons:

  • The use of the UI is ergonomic but requires a lot of manual actions, which, with many projects, can be very time- and resource-consuming.
  • In Terraform Cloud, the execution workflow in remote mode is fixed with the execution of the plan command, as well as the application. It isn't possible to add other actions (which we have studied in this book) such as the execution...