weekly.tf - Issue #83 - Terramate and Terragrunt, Terraform workspaces, Gitops, Scaling Infrastructure as Code Culture, Terraform Associate Certification

Sören Martius (CTO of Mineiros) published a detailed review of WHY Terramate was created in the first place. AB: Terramate is one of the competitors for Terragrunt and Terraspace that mostly implements features that should be in Terraform in the first place. Terramate currently has features like code generation, change detection, and some more complicated features (e.g. terragrunt config generations, change detection made within git branches). Look at the example code provided to make your own judgment, but I will continue using Terragrunt in all of my bigger projects where plain Terraform is not enough.

This article is focusing on reworking the Terraform code repository, which has been set up in a way called “Snowflakes as code”. AB: I think that the best way to enforce consistency with Terraform happens by promoting versioned artifacts (Terraform modules) via pipeline. More on this in Kief’s book “Infrastructure as code” (chapter 7) and this blog post.

This is one of the multiple detailed articles by Denilson Nastacio that provides a decision framework to help practitioners choose what to manage with GitOps and what to avoid. AB: I recommend reading this one to better understand how to manage certain types of data (it is relevant if you use Pulumi, too).