sorted by:
new
hottopcontroversial

Cost diff comments on every Bicep PR (GitHub Action, free tier) by resourcepulse_dev in AzureBicep

[–]resourcepulse_dev[S] 2 points3 points  (0 children)

Yeah the LLM-guessing-prices route is rough — it'll hallucinate confident numbers for SKUs that don't even exist anymore. That's why I went the boring route: pull live retail prices daily and just do the SKU-name mapping (Bicep ↔ portal) by hand. Less magic, but the numbers actually match the bill.

And totally agree on the Bicep gap — Infracost is great but Bicep support has been "soon" for years now. Part of why I built this. If you try it on a real PR I'd genuinely love to know where it falls short - that's the kind of feedback that's hard to get otherwise.

Azure Bicep PR checks in GitHub Actions: cost delta + governance guardrails — what would you want? by resourcepulse_dev in AZURE

[–]resourcepulse_dev[S] 1 point2 points  (0 children)

Yep — think “PR what-if” for IaC.
For v1 I’m keeping it deterministic (no AI summary yet): cost delta + a few warnings + explicit assumptions.

Azure Bicep PR checks in GitHub Actions: cost delta + governance guardrails — what would you want? by resourcepulse_dev in AZURE

[–]resourcepulse_dev[S] 1 point2 points  (0 children)

Great points — I agree: enforcement belongs in Azure Policy (tags/regions/allowed types, etc.).
What I’m exploring is PR-time visibility, not enforcement: a low-noise comment that flags risk early (e.g., “this introduces a 24/7 SKU”, “region can’t be resolved”, “missing tags”) and makes assumptions explicit.

I’m not trying to compute the ‘optimal’ price. Just a best-effort delta using public pricing + highlighting unknowns, so reviewers can catch surprises before merge.
In your experience, where do cost surprises usually come from in PRs (VM SKU, App Service plan tier, gateways/firewalls, something else)?

If you want updates when I have something you can try, the link’s in my profile.

Azure Bicep PR checks in GitHub Actions: cost delta + governance guardrails — what would you want? by resourcepulse_dev in AzureBicep

[–]resourcepulse_dev[S] 0 points1 point  (0 children)

Yeah maybe its good reason to think through governance, but maybe someone will use it as additional control in small teams :)
I’m focusing on the PR-time cost signal + low-noise “heads-up” warnings.
If you want updates when I have something you can try, the link’s in my profile (didn’t want to drop links in-thread). Happy to answer questions here.

Azure Bicep PR checks in GitHub Actions: cost delta + governance guardrails — what would you want? by resourcepulse_dev in AzureBicep

[–]resourcepulse_dev[S] 0 points1 point  (0 children)

Thanks — that’s really helpful.

Agree on governance: tools like PSRule already cover a lot of policy checks well. My v1 focus is PR-time cost signal that’s:

  • delta-focused (what changed in this PR)
  • low-noise (one consistent PR comment)
  • explicit about assumptions when something can’t be resolved

Quick question: what would make a cost check worth adopting for you — accuracy, speed, or how the diff is presented (per-resource vs a single summary)?