Cost Visibility for Infrastructure as Code
summary
Shows Infracost scanning Terraform plans pre‑apply and producing monthly cost estimates (example shown: ~$31 total) by calling the Infracost API with an API key stored in GitHub Secrets. Demonstrates a custom container action with Dockerfile and entrypoint that comments cost into PRs (requires GITHUB_REF PR number), installs terraform and infracost, and supports mono vs microservice layouts by looping through multiple terraform directories. Demo mostly works; PR comment step fails locally in one run.
AI-written summary · about
chapters (11)
- 0:00Cost visibility intro
- 1:51What is Infracost and how it works
- 4:42Infracost for GitHub Actions
- 7:15Custom GitHub Action container
- 10:50Microservice infrastructure changes
- 15:05Monorepo action adaption
- 17:12Terraform demo setup
- 19:50Live Infracost plugin
- 22:13GitHub Action pipeline run
- 24:56Summary
- 25:59Q&A
related talks
29mCost Visibility for Infrastructure as Code
27mCode Smarter, Spend Wiser: Infracost & Open Tofu Unleashed
37mInfraCoding with Terraform: Writing Tests for Infrastructure-as-Code
22mEnabling Infrastructure as Code
44mEvolution of Infrastructure Management
01h 00mSecurely deploying Infrastructure as Code
36mInfrastructure as Code with Terraform
24mTerraform Best Practices