ref: Add protos fields for customer subscription API#322
Merged
Conversation
|
The latest Buf updates on your PR. Results from workflow ci / buf-checks (pull_request).
|
armenzg
approved these changes
Jun 22, 2026
|
|
||
| // Whether the org has a soft cap: usage past reserved volume is allowed | ||
| // (and billed) instead of hard-stopping ingestion. | ||
| bool has_soft_cap = 10; |
Member
There was a problem hiding this comment.
Do you know if we intend to preserve soft caps? or if we currently use it?
Contributor
Author
There was a problem hiding this comment.
It is used so I think we should try and support it, would operate on the assumption that we are supporting it for now and can re-evaluate later if it needs to be dropped
4 tasks
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.
These fields will be needed as part of the customer details API