Implement LRU Caching for OpenID Configuration Discovery #4
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.
Implement LRU Caching for OpenID Configuration Discovery
Summary
Optimizes the
get_discovery_docfunction by adding LRU caching to eliminate redundant HTTP requests to.well-known/openid_configurationendpoints. Since OpenID configuration is stable and rarely changes, this reduces latency and potential failure points when creating multipleAuthClientinstances.Key Changes:
@lru_cache(maxsize=128)decorator toget_discovery_docfunctionsessionparameter - function now always usesrequests.getdirectlyAuthClient.__init__to call function without session parameterReview & Testing Checklist for Human
High Priority (3 items):
AuthClientinstances with same environment and confirm only one HTTP request is made to discovery endpointNotes
Link to Devin run: https://app.devin.ai/sessions/b279b98117be48f9b5f30414a34ea9ea
Requested by: @abhay-codeium