weekly.tf - Issue #58 - CI/CD in GCP, Terragrunt features without terragrunt
Do you wonder how does TIER manage access control for humans inside Kubernetes, using their AWS roles? Everything is managed like infrastructure code.
CI/CD pipelines generally consist of stages for building, unit/integration testing, publishing, and deploying applications on multiple environments (e.g., dev, staging, prod). This article describes the process step by step.
A detailed overview of the validation technics which can be done for variables in Terraform. AB: I use this feature very seldom because of its statically limited scope (no data source or other variables can be accessed). Use tflint if you want to validate something more dynamically.
Terragrunt features without terragrunt, please!
Many of us who were using Terraform for some time (especially since pre-0.12 times), used to develop and operate a variety of wrappers because Terraform CLI didn't have certain features we wanted (or we thought "we wanted").
Terragrunt is the most popular tool in this category (see my review part 1 and part 2) but it is not the only one. There is also Terraspace by Boltops that I had the pleasure to review with the author a year ago (link).
I believe that most of the existing wrapping solutions are unnecessarily hard to use (prove me wrong on Reddit).
Do most of the users really need features provided by the Terragrunt or should we aim to extract just 20% of them and have them incorporated in the Terraform at some point?
Read PHILOSOPHY.md before you decide that this project is a terrible idea. There are a lot of valid points you can pick up for your next argument with someone telling you that "terragrunt is great, simple and you should use it right away!" :)
Do you like this newsletter? Think about sharing it on social media and providing your feedback to me (e.g., @antonbabenko or reply to the email). I want to know it!