Infracost scans for Terraform code changes and checks over 3 million prices to create a simple, understandable cost estimate before any resources are launched.

Infracost Community

Morning Joerg :coffee: ,

There’s no “right” answer here. It’s up to your personal preference. In general, I recommend going with the config file approach. Scanning each folder and posting a new comment can be quite noisy on the PR. Especially if authors update PRs as part of code review. This inevitably leads to frustration. So my feeling is to start off with the config file, and then if you want more verbosity, change to running for each project.

Hope this helps