Atlantis and OpenTofu: The Future of Open-Source IaC - PePe Amengual, Slalom & Dylan-Daniel Page

Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon North America in Salt Lake City from November 12 - 15, 2024. Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io
Atlantis and OpenTofu: The Future of Open-Source IaC - PePe Amengual, Slalom & Dylan-Daniel Page, Lambda Labs
Atlantis is an open-source tool that enhances collaboration and automation in the realm of Infrastructure as Code (IaC). Designed to integrate seamlessly with version control systems like Git, Atlantis empowers teams using Terraform to manage and provision infrastructure efficiently. With its user-friendly interface and automated workflows, Atlantis streamlines the process of reviewing, validating, and applying Terraform changes. This application facilitates a collaborative approach to infrastructure management, allowing teams to work together on defining and deploying infrastructure changes with confidence. Atlantis not only enhances the Terraform workflow but also promotes best practices in IaC development, making it a valuable asset for DevOps teams seeking to optimize their infrastructure processes. As OpenTofu evolves over time, the Atlantis project is excited about the new collaborations.

[@absolutejam]

Atlantis seems really interesting, but isn’t it an anti-pattern to apply change outside of a CD pipeline?

[@thegarageetc]

outside a cd pipeline? Atlantis runs and Interact with your PR the closest to the code possible

[@absolutejam]

@@thegarageetc But it’s outside the actual CI/CD pipeline as it’s in the comments and lives outside the normal ‘build, test, deploy’ flow.
I generally perform a ‘plan’ as part of CI pipeline (on merge requests) and trigger the ‘apply’ on merge into main (CD), meaning it’s fully integrated and can’t have result in a workflow mismatch (ie. Running apply then the MR not being merged)

[@thegarageetc]

@@absolutejam this is a PR base system, all those steps you talk about start with a PR too so I see no reason why on the same pr you can't have tests, ci or others, those could be parallel and required for the status to be mergeable