Repository navigation
Conversation
The auto top-up config mixed two settings: when to buy more Seer credit, and a daily cap on spending. SeerWalletConfig keeps them as separate AutoTopUpConfig and SpendConfig messages behind one upsert endpoint. A section the upsert request leaves unset keeps its stored value, so either can be saved without touching the other. The spend cap is in cents before tax rather than credits. The Wallet enum is dropped because the service only covers the Seer wallet.
Each section of the config is stored on its own, so there is no single config row for an id to name.
The job lists organizations with auto top-up enabled, then asks SeerWalletService to top up each one whose balance is below its threshold. It skips an organization whose last top-up invoice is still unpaid, which needs ListInvoices to filter by client_id.
…ervice Define the service boundary that saves wallet settings and reports the immediate refill result when a customer turns auto top-up on. Include payment failure and 3D Secure details so callers can complete an unsuccessful synchronous charge. Constraint: Keep the recurring auto-top-up invoice flow as the single billing implementation Confidence: high Scope-risk: narrow
|
The latest Buf updates on your PR. Results from workflow ci / buf-checks (pull_request).
|
volokluev
changed the base branch from
volo/seer-wallet-auto-top-up-job
to
main
November 9, 2026 20:51
This branch has not been deployed
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.
Summary
Testing
make build-pyStacked on the proto branch used by getsentry/getsentry#23035.