Skip to content

feat(billing): added account protos(REVENG-79)#254

Merged
krithikravi merged 3 commits into
mainfrom
account-status-proto
May 12, 2026
Merged

feat(billing): added account protos(REVENG-79)#254
krithikravi merged 3 commits into
mainfrom
account-status-proto

Conversation

@krithikravi
Copy link
Copy Markdown
Member

https://linear.app/getsentry/issue/REVENG-79/create-accountstatus-proto

This PR adds protos for an account's status, which represent org-wide information not contained on the contract such as org status, soft cap eligibility etc.

@krithikravi krithikravi requested a review from a team as a code owner May 11, 2026 23:45
@linear-code
Copy link
Copy Markdown

linear-code Bot commented May 11, 2026

REVENG-79

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 11, 2026

The latest Buf updates on your PR. Results from workflow ci / buf-checks (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedMay 12, 2026, 4:54 PM

message AccountStatus {
// The organization this status belongs to. Each org has one AccountStatus.
uint64 organization_id = 1;
// Legacy soft cap flag. When true, no category is rate-limited regardless of usage.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we still need a legacy flag on billing platform?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just referencing the fact that softcaps can now be enabled per category, previously the 'legacy' version applied to the whole subscription and just meant we didn't rate limit them at all. We still use this for use cases like giving an unlimited trial to enterprise orgs that are on a subscription trial etc.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that will end up being managed by the new trials service and not by this flag now

// Current account status (active, closed, past-due).
Status status = 3;
// Whether the account is suspended by an admin (e.g., for fraud).
bool is_suspended = 4;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this redundant with the status enum?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we currently store this in the existing codebase separately, but i'm fine with merging them tbh

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit c1e8673. Configure here.

Comment thread proto/sentry_protos/billing/v1/services/account_status/v1/account_status.proto Outdated
@krithikravi krithikravi merged commit 04a19f3 into main May 12, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants