Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to choose an Infinispan cache for the limits instead of creating one #44

Merged
merged 3 commits into from
Jun 1, 2021

Conversation

davidor
Copy link
Contributor

@davidor davidor commented Jun 1, 2021

This PR makes changes both in the lib and the server to allow users to choose the Infinispan cache that they'd like to use. In the server side there's a new ENV, INFINISPAN_CACHE_NAME for this. In the lib, I added a new builder for the InfinispanStorage struct that accepts a cache name.

@davidor davidor requested a review from unleashed June 1, 2021 09:08
Copy link
Contributor

@unleashed unleashed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - check out comments

@@ -31,6 +31,16 @@ variables:
- Format: integer.


## INFINISPAN_CACHE_NAME
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The amount of environment variables is starting to get out of hand... :)

Yes, this is intended to be run with its own container image, but perhaps it would be good to look into also accepting a configuration file providing fallback settings for missing envs?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should consider that. There are more config params coming :D

@davidor davidor merged commit 21ec621 into master Jun 1, 2021
@davidor davidor deleted the infinispan-with-given-cache-name branch June 1, 2021 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants