Many readers know about terraform-aws-modules as a collection of 43 Terraform AWS modules with 100M+ provisions supported by the community (see Terraform Registry).
If you enjoy the modules we’ve created please give them a ⭐ and have your friends give them a ⭐ - and if your organization uses the modules to run their infrastructure, have them consider supporting through sponsorship. Cheers!
Running Terraform from Terraform is now possible via Terraform provider (no need to use “hacks” with null_resource provisioner). AB: But why? To “emulate” terragrunt apply-all, or to generate Terraform code before running it when something is impossible to customize (e.g., usage of variables in the lifecycle block). “Terraform-native Terragrunt” - Valentin Petrov wrote in the comments. Anton_should_put_some_disclaimer_here
Brendan Thompson described a few methods of ingesting configuration into your Terraform code or modules to help you deliver infrastructure in a more consistent and repeatable manner. tldr; YAML/JSON vs tfvars vs usage of higher-order modules.
Steven Aldinger from TeamSnap described how they handle changes in Terraform module repositories by using conventional commits, semantic releases, Dependabot, and GitHub Actions. AB: Dependabot can handle private repositories since March 2021!
Spacelift in Action - How to manage IaC in increasingly complex and dynamic environment - Part 2
Feedback ❤️
Do you like this newsletter? How 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!