feat(model): add master token accessor#347
Draft
bussyjd wants to merge 1 commit intofeat/x402-pre-merge-followupfrom
Draft
feat(model): add master token accessor#347bussyjd wants to merge 1 commit intofeat/x402-pre-merge-followupfrom
bussyjd wants to merge 1 commit intofeat/x402-pre-merge-followupfrom
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.
Summary
Adds
obol model tokenas a direct accessor for the LiteLLM master token stored in-cluster.Why
Production-readiness testing found that API consumers currently have to discover the LiteLLM master token by reading the
litellm-secretsSecret manually viaobol kubectl get secret .... This PR turns the existing internal accessor into a supported CLI path.What changed
model tokensubcommand{"token": ...}in JSON modecmd/obol/model_test.goValidation
go test ./cmd/obol