Скачать или смотреть 👩‍💻 Use IaC and Terraform to structure & test your Terraform code

Learn Infrastructure-as-code and Terraform to structure and test your Terraform code

Working with a team of Cloud architects and DevOps, implies contributing to many Terraform repositories. It also means that we’ve to do code review to keep our code clean.

This process can be time-consuming and challenging.

Our time is precious, and we must not waste it.

Here are some good practices we can implement to be able to handle more code with less effort.

1️⃣ Design to code

We design our architecture & write clear and concise Terraform code that matches the design patterns already in place.

2️⃣ Always test, format and validate

As with all other code, IaC code should be tested properly. There are different approaches here, and again, we should find one that makes sense for us.

Running Terraform Plan can be useful to properly format our code and catch any issues that we could have missed.

3️⃣ Set-up State locking for team collaboration

What if two team members execute Terraform commands at the same time? This can lead to the corruption of the terraform state file or even data loss.

The locking mechanism helps to prevent such scenarios. It makes sure that at a time, only one person is running the terraform configurations, and there is no conflict.

4️⃣ Host Terraform code in Git Repository

When we’re working on Terraform code with our team it’s important to share the code in order to collaborate effectively. Just like our application code.

Git is a version control system used to track changes made to files or projects over time. Git records the changes made in a special database named repositories. This allows us to look at our complete project history to see who made changes and why. This is especially useful in a production environment where different people have to work on the same project, and makes sure everyone is working on the latest version of the file.

✅ Exactly as application code
✅ History of infrastructure code changes to make sure everyone is working on the latest version of the file.
✅ For Successful team collaboration

We can use either GitHub, GitLab, AzureDevOps and / or Bitbucket.

5️⃣ Meta-arguments

To manage several resources, we can use either count or for_each, which removes the need to write a separate block of code for each one.

Count: If the resources we are provisioning are identical or nearly identical, then we can use count.

However if elements of the resources change between the different instances, then we can use for_each.

Depends_on allow us to specify dependencies between resources and modules.

By using these meta arguments, we can make our code

✅ More structured
✅ More efficient

To save valuable time and effort.

You can start testing different scenarios here 👉https://app.brainboard.co

#terraform #cloud #cloudcomputing #aws #azure #gcp #solutionarchitect #cloudarchitect #training #neverstoplearning #100daysofcloud