weekly.tf - Issue #93 - No one should write Terraform (agree?), Kitchen Terraform, Atlantis, Policy Automation with Conftest, Grafana alerting, Barbe
Please enjoy the Terraform Weekly newsletter and share it with your peers if you like it. I will probably see some of your at HashiConf Global in Los Angeles (October 4-6, 2022).
Leon Wright wrote a reflection upon zwischenzugs' insightful and thought-provoking article “Who should write the Terraform?”, the TL;DR conclusion Leon came to was “No One”. AB: I do not fully agree with the author because to me the key to productivity with Terraform lies in using building blocks (modules) and not hoping that by using CDK for Terraform the underlying Terraform limitations will automagically go away. The cover image was made by me.
Apurva Shingne and Prajakta Shete described a way to start testing your Terraform code and explained why it’s helpful in preventing issues before they become bugs. AB: Unfortunately, Kitchen Terraform is still not integrated with terraform test command natively.
AB: This post explains the life before Atlantis, deployment of Atlantis on Kubernetes cluster, and running it happily with Terragrunt. Short but rather insightful post.
Lin Du and Juvenal Santos described how DoorDash enables its engineers to self-serve infrastructure through policy automation while ensuring reliability and speed. AB: They use Atlantis with Conftest.
Alex Weaver explains how Terraform provider support for Grafana Alerting makes it easy to create, manage, and maintain your entire Grafana Alerting stack as code.
A serverless application development solution backed by Terraform. AB: If you want to write fewer lines and don't mind introducing one more abstraction, this can be for you.
Remember that sharing is caring, so it will help the Terraform community (and me) if you share this newsletter with your friends and colleagues.
PS: One of the best ways to help Ukraine - https://palianytsia.com.ua/
Glory to Ukraine! 🇺🇦