Repository navigation
feat: support per-request API-key providers - #26
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.
Summary
Add
ClientOptions.api_key_providerto resolve an API key asynchronously for each HTTP attempt, including retries. Results are not cached, and provider failures stop the request without retrying. Existing client modes remain supported.Includes usage documentation and tests for HTTP retries, concurrent requests, cancellation, provider failures, and seller factories.
Validation
Passed
make syncandmake verify, including Ruff formatting and lint, strict type checking, the full test suite, per-file coverage checks, and built-distribution consumer tests.No release is performed by this PR.