We released major improvements to the tagging policies feature to simplify identifying and fixing tagging issues. We also re-designed the Infracost report emails to summarize key changes across your repos. The CLI also got many bug fixes and big performance improvements.
New feature announcement: FinOps tags can now be checked directly in the engineering workflow in CI/CD, before anything goes to production, by shifting them left. Both the key and value can be verified. If the tagging policy has not been followed, the engineer will be notified and the code pull request can be blocked until it is fixed.
We recently released a new GitLab App that enables you to quickly add Infracost to all of your repos with a few clicks. We also released a new Jira app so product managers and budget owners know the cost impact of a feature request or change, before deployment! There's also a new version of the VS Code extension, and the ability to export costs to AWS S3 & Azure Blob Storage.
Last month we made a big push to add more than 100 resources across AWS, Azure and Google. Infracost Guardrails now enable you set thresholds against projects inside pull requests. There's also a new Viewer role, so you can add engineering teams to the view all cost changes, guardrails, and policies.
The all-new Infracost Guardrails now enable you to approve and unblock pull requests (PRs) that were blocked by the budget guardrail. This month's release includes dynamic and org-level config files, which will help with repos that have multiple Terraform projects (e.g. mono repos or teragrunt repos). We have also added support for more AWS and Azure resources, taking our total coverage to over 1,000 Terraform resources! Additionally, you can now set the PR status for GitLab & Azure Repos to merged, and view PR histories in Infracost Cloud.
We kicked-off 2023 by doubling down on helping companies optimize cloud costs by assisting engineers directly in CI/CD workflows.
We started tracking cost savings from Guardrails. We also made Infracost run faster for by only running on changed directories, caching modules, and running projects in parallel. On top of that, we made numerous bug fixes to make Terragrunt support more robust, and released support for single sign-on.