Repository navigation
feat(billing): Expose when PAYG spend exceeds its budget - #482
Merged
Merged
Conversation
|
The latest Buf updates on your PR. Results from workflow ci / buf-checks (pull_request).
|
hybrendan
marked this pull request as ready for review
October 26, 2026 21:48
armenzg
approved these changes
Oct 27, 2026
4 tasks done
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
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.
Add
exceeded_payg_budgetto usage pricer summaries so callers can distinguish an exact budget fit from spend that actually needs capping. For example, a $1 allocation against a $1 budget exhausts the budget but does not respond withexceeded_payg_budget=true.Also, deprecates unused
reserved_budget_exhaustedandpayg_budget_exhaustedsincehas_remaining_capacitycovers them