refactor(improvement): use secret URI as key for cache and refactor lrucache#12682
Merged
Conversation
dosubot
Bot
added
size:L
Revolyssup
marked this pull request as draft
October 16, 2025 18:07
Revolyssup
changed the title
Revolyssup
marked this pull request as ready for review
October 17, 2025 06:35
nic-6443
reviewed
Oct 18, 2025
nic-6443
approved these changes
Oct 18, 2025
membphis
approved these changes
Oct 23, 2025
AlinsRan
approved these changes
Oct 23, 2025
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
4 participants
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.
Secret module changes: Currently the cache key is the whole conf which is inefficient because multiple conf might be referencing the same secret.
So new requirement is to refactor apisix/secret.lua so that cache key is the url and we only cache the result of fetch(uri) function.
LRUCache module changes: Allow LRU cache to have different underlying cache for success and failure, so that each of them can be configured differently.
NOTE: The fetch_secrets() API is simplified to not take key and version from the caller because they were redundant anyways and moreover now the key is resolved internally.
Checklist