7. Collaborative Infrastructure | Getting Started with Terraform

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Getting Started with Terraform

By : Kirill Shirinkin

2 (1)

Getting Started with Terraform

2 (1)

By: Kirill Shirinkin

Overview of this book

Terraform is a tool used to efficiently build, configure, and improve production infrastructure. It can manage existing infrastructure as well as create custom in-house solutions. This book shows you when and how to implement infrastructure as a code practices with Terraform. It covers everything necessary to set up complete management of infrastructure with Terraform, starting with the basics of using providers and resources. This book is a comprehensive guide that begins with very small infrastructure templates and takes you all the way to managing complex systems, all using concrete examples that evolve over the course of the book. It finishes with the complete workflow of managing a production infrastructure as code – this is achieved with the help of version control and continuous integration. At the end of this book, you will be familiar with advanced techniques such as multi-provider support and multiple remote modules.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Infrastructure Automation

1. Infrastructure Automation

What is Infrastructure as Code and why is it needed?

Declarative vs Procedural tools for Infrastructure as Code

Infrastructure as Code in the Cloud

Requirements for infrastructure provisioner

Which tools exist for infrastructure provisioning?

A short overview of Terraform

Journey ahead and how to read this book

Summary

2. Deploying First Server

2. Deploying First Server

History of Terraform

Preparing work environment

The many Terraform providers

Short introduction to AWS

Using Elastic Compute Cloud

Configuring AWS provider

Creating EC2 instance with Terraform

Working with state

Handling resource updates

Destroying everything we've built

Summary

3. Resource Dependencies and Modules

3. Resource Dependencies and Modules

Creating AWS Virtual Private Cloud

Understanding dependency graph

Playing with Terraform graph

Controlling dependencies with depends_on and ignore_changes

Making sense of our template

Removing duplication with modules

Configuring modules

Retrieving module data with outputs

Using root module outputs

Summary

4. Storing and Supplying Configuration

4. Storing and Supplying Configuration

Understanding variables

Configuring data sources

Exploring Terraform configuration resources

Taking a quick look at Consul

Summary

5. Connecting with Other Tools

5. Connecting with Other Tools

Returning data with outputs

Testing servers with Inspec

Provisioners

Reprovisioning machines with null_resource

Using third-party plugins

Summary

6. Scaling and Updating Infrastructure

6. Scaling and Updating Infrastructure

Counting servers

Bringing in high availability

Load balancing and simulating conditionals

Immutable Infrastructure

Baking images with Packer

Rolling out AMI upgrades with Terraform

Performing blue-green deployments

Refreshing infrastructure

Importing resources

Summary

7. Collaborative Infrastructure

7. Collaborative Infrastructure

Version control with Git 101

Moving templates to Git

Protecting secrets in a Git repository

Storing state files remotely

Connecting remote states together

Storing modules remotely

Locking state files with Terragrunt

Moving infrastructure updates to the CI pipeline

Integration testing of Terraform modules

Summary

8. Future of Terraform

8. Future of Terraform

Infrastructure as Code and Terraform replacements

Learning AWS and compiling Terraform

Learning Consul

Provisioning and configuration management

Immutable Infrastructure

Collaboration and CI/CD

The many tools around Terraform

The rapid development of Terraform

Closing thoughts on the future of Terraform

Summary

Customer Reviews

2 (1)

5 star

0

4 star

0

3 star

0

2 star

100%

1 star

0

Locking state files with Terragrunt

Let's say you have your application template and a team of five people working on it. One Monday morning you decide to change a minor thing, such as the security group, and at the same time your colleague, sitting in a room next to you, decides to change a disk size for instances. Being confident that you are the only ones running the terraform apply command at this moment, you both do terraform apply, push changed state file to the git repository (or to remote storage like S3), and end up in a total disaster.

If your state file is stored in git, then you will meet the merge conflict: not too bad, you can try to resolve it by hand, and you still can see who changed what. If you use a remote backend for the state file, then things are going south. Which state file is now inside the remote storage? And where do changes of another Terraform run go?

It is dangerous to work on the same state file in a team because there is no locking out of the box. You could...

Search

Your notes and bookmarks