Set initial token spending limits in CLI and dashboard - #86
Merged
Merged
Conversation
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
1 participant
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.
Allow
ow token create --name experiment --spending-limit-usd 100and dashboard token creation to set a lifetime USD budget. A new RPC creates the token and budget atomically, preserving existing token-creation authorization while keeping existing-budget changes restricted to admin users.Validate nonnegative finite amounts, including a zero budget. Document budget exhaustion: cancel queued/running jobs for the key, preserve completed jobs and other keys' work, and reject new submissions. Add PostgreSQL tests for atomic rollback, authorization, and the 100-job/60-completed scenario, plus CLI/API tests.
Validation: 97 tests passed with isolated PostgreSQL; frontend build and Chromium startup passed. Release 0.13.3 requires the additive token-creation RPC migration; worker images remain v0.13.1.