Why Terraform Workflows Break Down Across Multiple Teams

This story was originally published on HackerNoon at: https://hackernoon.com/why-terraform-workflows-break-down-across-multiple-teams. How to centralize Terraform across multiple teams. Shared state and OIDC federation, one execution model, policy as code, and drift detection you can schedule. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #terraform, #devops, #infrastructure-as-code, #engineering, #terraform-governance, #terraform-at-scale, #terraform-workflows, #hackernoon-top-story, and more. This story was written by: @mariusz_michalowski. Learn more about this writer by checking @mariusz_michalowski's about page, and for more stories, please visit hackernoon.com. Centralizing Terraform means putting state and credentials, execution, policy, and visibility under shared ownership, which can be achieved by using a remote state backend, OIDC federation, reusable CI workflows, and policy as code.