feat: Add EL support for the cache resource field #112
+13
−3
Conversation
This file contains 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
oleksii-bielik
force-pushed
the
issue/#9697-gravitee-oauth2-policy-el
branch
from
4a511f2
to
6aceaa8
Compare
oleksii-bielik
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
gravitee-io/issues#9697
Description
Currently the "OAuth2 resource" supports EL and we can dynamically set the resource name, for example, based on the tenant. Unfortunately the "Cache resource" doesn't support EL and we're limited because of this. Especially when we use Redis cache, it's hard to use a proper Redis instance based on the region with current functionality.
In this PR I add EL support for the "Cache resource" field
Thanks