3 ms·
> I don't really see how you'd be able to improve this situation, either I have to assume they could model some projections based on your current usage, and gi
by rattray 4y ago
> I don't really see how you'd be able to improve this situation, either
I have to assume they could model some projections based on your current usage, and give you that? Predicting the future is hard, of course, but if their algorithm is simple & basic enough to understand, it'd surely be quite helpful, no?
- Arbortheus 4y agoSure, but that only works if you’re modifying an existing piece of infrastructure. If I’m creating a new cloud function they have no idea if it’s getting invoked once per week or once per second.
- rattray 4y agoAh, good point! That definitely does sound tricky. Might be cool to see some syntax where you encode your estimates, and it sends an async warning of some kind when the estimates are wildly off? resource "aws_lambda" "foo" { estimated_invocations = {p5: "1 per hour", p95: "100 per minute"} # or estimated_invocations = {avg: "5 per minute"} } Then you might get a range estimate of some kind, and maybe even an automated pull request with the real numbers if you're way off?
- akh 4y agoVery cool idea! Some created a prototype with Terragrunt (https://github.com/infracost/infracost/issues/463#issuecomment-801010858 https://github.com/infracost/infracost/issues/463#issuecomme...). With Infracost parsing HCL directly, we might be able to introduce annotations for estimates -> alerts