Speed Up and Save Your Terraform/OpenTofu/Terragrunt with Caching Provider Binary

As many already knows, terraform will download the provider binary from the internet when we run terraform init / tofu init / terragrunt init command each time we invoke it in newly directory or project. This is a good thing, but it can be a problem when we have a slow internet connection or when we have a lot of providers to download or you have terragrunt monorepo that will be run in sequence, simply complex terraform or IaC dependency. This is where the caching provider binary comes in handy and will help you. Your project .terraform directory will have symbolic link to the provider binary in the cache directory.

SOPS + Age a Perfect Twin Brothers for Cost Effective Secret Management in Git

Background

When I moved to my current company, I was shocked and a bit irritated by the current condition in the infrastructure side. The infrastructure was not well-organized and documented, there is no Infrastructure as Code (IaC) that I love so much.

I started to introduce and initiate the IaC, and in the process I found that I need to manage the secrets. At first, I want to use GCP Secret Manager / GCP KMS, like what I know in AWS, we can use AWS Parameter Store / AWS KMS to do encryption and storing secrets but it’s not cost effective at current scale and condition, we faced.