"GitOps for Infrastructure"
summary
Demo shows an AWS account and an Amazon VPC created end-to-end by pull request: Git triggers a Terraform plan then an approval (console or Slack) and a Terraform apply executed via a Harness delegate into the target account. The PR creates 104 resources for the VPC, IAM roles and AD/ADFS wiring, with cross-account execution and CloudTrail + Slack alerts for manual changes. All changes are auditable and revertible only by creating a new PR, enforcing declarative, Git-backed self‑service.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:22Agenda
- 1:07Demo
- 6:34About Line Data
- 9:42Devsecops
- 12:05Group level responsibility
- 15:37GitOps
- 18:06Operating Model
- 19:33Terraform
- 21:35In practice
- 33:42Challenges
- 38:43Revert
related talks
35mGitOps in Action
02h 02mAn end-to-end GitOps Architecture: Terraform, Ansible, Kubernetes and AWS
17mUsing GitOps for Both Infrastructure and Applications
15mTerraform, GitOps & Kubernetes: manage infrastructure & aas
37mFrom IaC to InfraOps: Automating Day-2 Operations with Terraform Actions & Ansible
35mGitOps - Operations by Pull Request
16mWant to extend GitOps to Infrastructure and Workloads? Here's how.
23mFully SaaS-Based DevOps with Terraform Cloud and GitLab