What does HackerNews think of infracost?
Cloud cost estimates for Terraform in pull requests💰📉 Love your cloud bill!
> HashiCorp considers a competitive offering to be a product or service provided to users or customers outside of your organization that has significant overlap with the capabilities of HashiCorp’s commercial products or services.
So, consider there is no cost estimate service and you built a thing that got popular (https://github.com/infracost/infracost). Then after 2 years Terraform Cloud catches up. What happens? Are you out of business?
Whilst this might sound funny, we were surprised to see it as a common use-cases with users putting https://github.com/infracost/infracost in their CI/CD pipelines to act as safety net. Currently it only works for Terraform users, but we plan to add other infra-as-code tools in the future. We're also discussing how we can do this for people who don't use infra-as-code in https://github.com/infracost/infracost/issues/840 but it's not clear what the workflow could look like for them. Perhaps having separate AWS accounts with a budget alert that emails you to run https://github.com/rebuy-de/aws-nuke is a work-around just now.
(I'm co-founder of Infracost)
> tie the pain directly to the folks who can fix the problem
That's why we're building https://github.com/infracost/infracost for engineering teams (free open source)
We're trying to do a similar thing by putting a comment in PRs (e.g. for Terraform repos) to say how much the cost of the change will be before it goes live (we're open source https://github.com/infracost/infracost). Always interested in hearing what people think about this approach.
We're trying to tackle this problem with https://github.com/infracost/infracost from another angle for people who use Terraform: show a cost estimate in pull requests so the user understands what costs money, and roughly how much it costs. I hope that helps clarify "only pay for what you use" without trawling through cloud pricing pages.