{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Terragrunt Parallel Apply in GitHub Actions: 2.7× Faster","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/faf7ac81\"></iframe>","width":"100%","height":180,"duration":577,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/terragrunt-parallel-apply-in-github-actions-27-faster.\nHow inDrive used dependency graphs and GitHub Actions for Terragrunt parallel apply, achieving 2.7× aggregate speedup over an estimated serial baseline.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #terraform, #terragrunt, #github-actions, #infrastructure-as-code, #devops, #aws, #automation, #good-company,  and more.\nThis story was written by: @indrivetech. Learn more about this writer by checking @indrivetech's about page,\n            and for more stories, please visit hackernoon.com.\nAt 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.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}