Send identity token + adopt server usage counts - #64
Merged
Conversation
- resolveIdentity stores the identity_token issued by authUserCheck - callBuildShip sends Authorization: Bearer <identity_token> - ensureIdentityReady gates pipeline start (5s cap) so generation never fires before a token exists - generator responses with usage_status=success adopt the server count as authoritative; local+1 only as fallback when absent
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.
Pairs with buildship#80. Stores the identity JWT from authUserCheck, sends it as a Bearer header on pipeline calls, gates generation on identity resolution, and adopts the server's authoritative usage_count when present (local+1 fallback only). 206/206 tests pass.