feat(rules): add forecasted budget breach guardrail - #179
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
Author
No action required: this is a review status update, not a code finding. |
roborev: Combined Review (
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CloudBurn can now flag a budget whose same-unit forecast is above its limit while actual spend hasn't crossed the limit yet. It doesn't emit the forecast finding after the budget has already breached, because
COSTGUARDRAILS-3covers that state.This PR reuses the budget data CloudBurn already loads, so it doesn't add AWS calls or IAM permissions. Per-budget evaluation evidence is wired to the same resource set as the existing exceeded-budget rule.
Notification and subscriber coverage isn't included in this slice and remains open in #167.
Scope
cloudburn(cli)@cloudburn/sdk@cloudburn/rulesRelease Notes
.changeset/*.mdfile for published package changesVerification
pnpm lintpnpm typecheckpnpm testpnpm buildpnpm verifypnpm docs:testBoundary Checks
@cloudburn/rulesRelated Issues
Part of #167.