The CloudBurn GitHub App reads the CDK diff or Terraform plan that a commenter action posts on your pull request, prices the resource changes against live AWS Pricing data, and replies with one cost report comment. It never clones your repository or reads your files — the pull request comment is the entire integration contract.
How it fits together
Two GitHub Actions produce the comments the app consumes:
| Action | Produces |
|---|---|
| aws-cdk-diff-pr-commenter | CDK diff comment per stack |
| terraform-plan-pr-commenter | Terraform plan comment per workspace |
Both actions also embed your repository's .cloudburn/usage-assumptions.json into the comment, so the app can price usage-billed services like S3, SQS, and SNS from numbers you control instead of guessing.
What the report contains
The cost report separates three confidence classes and never blends them:
- Fixed components price capacity that the diff declares outright, like an instance class or provisioned IOPS.
- Assumed components price workload-driven usage from your assumptions file, and each one names the value, unit, and scope that supplied it.
- Unknown components state which input is missing. A report with unknown components labels its subtotal as incomplete instead of pretending the cost is zero.
What's next
| Read this | To learn |
|---|---|
| Usage assumptions schema | Every field .cloudburn/usage-assumptions.json supports |
| Set up PR cost estimation | Installing and linking the app from your dashboard |
| CloudBurn Cloud overview | The rest of the managed product this app belongs to |
| Rules documentation | The cost checks CloudBurn runs against your infrastructure |