Skip to content
Artwork for Programming Tech Brief By HackerNoon
Programming Tech Brief By HackerNoon · Yesterday · 9 min

Terragrunt Parallel Apply in GitHub Actions: 2.7× Faster

This story was originally published on HackerNoon at: https://hackernoon.com/terragrunt-parallel-apply-in-github-actions-27-faster. How inDrive used dependency graphs and GitHub Actions for Terragrunt parallel apply, achieving 2.7× aggregate speedup over an estimated serial baseline. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #terraform, #terragrunt, #github-actions, #infrastructure-as-code, #devops, #aws, #automation, #good-company, and more. This story was written by: @indrivetech. Learn more about this writer by checking @indrivetech's about page, and for more stories, please visit hackernoon.com. At inDrive, we replaced order.txt with a validated dependency graph and parallel Terragrunt jobs in GitHub Actions. Across 355 rollouts, parallel apply took 64 hours versus an estimated 171 hours for serial execution—a 2.7× aggregate speedup. Small PRs often ran slower, so serial apply remains the default.

0:00-9:37

transcript

No transcript — this publisher did not publish one.

show notes

This story was originally published on HackerNoon at: https://hackernoon.com/terragrunt-parallel-apply-in-github-actions-27-faster.
How inDrive used dependency graphs and GitHub Actions for Terragrunt parallel apply, achieving 2.7× aggregate speedup over an estimated serial baseline.
Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #terraform, #terragrunt, #github-actions, #infrastructure-as-code, #devops, #aws, #automation, #good-company, and more.

This story was written by: @indrivetech. Learn more about this writer by checking @indrivetech's about page, and for more stories, please visit hackernoon.com.

At inDrive, we replaced order.txt with a validated dependency graph and parallel Terragrunt jobs in GitHub Actions. Across 355 rollouts, parallel apply took 64 hours versus an estimated 171 hours for serial execution—a 2.7× aggregate speedup. Small PRs often ran slower, so serial apply remains the default.

links13