Talk
Virtual
I coded 47 different IaC pipelines before coming up with the ultimate one
Have you ever had a member from a different team come to you with "The pipeline doesn't apply my changes! Why?" Having to maintain pipelines in sync with the ever-growing infrastructure? Let me show you how to solve that.
CEST
Meet the speakers
It always starts simply: a few cloud resources declared in Terraform, and a small pipeline that authenticates to the cloud and runs "cd $TF_PATH; terraform init; terraform apply".
But in six months, teams may be managing 20 separate environments in Terraform, buried in a sprawl of subfolders, for teams that create new projects faster than they can say "terraform apply".
In this talk, the speaker shows how to create a universal, scalable, and reusable Terraform pipeline with a little bit of magic:
• Auto-detect which environments have changed in a pull request, without any lists
• Execute jobs in parallel with matrix strategies
• Scan, validate, and detect security flaws in code
• Require manual approval for production deployments
Attendees will leave with the knowledge needed for a pipeline that scales from 3 to 30+ environments without touching the code.
