Move from redis to valkey #89
Merged
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
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.
See #74
This PR updates the actinia setup to use valkey instead of redis. It contains only functional adjustments, a lot of functional and semantic adjustments in the other actinia repos are still needed. See actinia-core/issues/573
Even though the alpine version was tested with actinia-core with valkey (per debugger in redis_base) instead of redis, it can already be merged as it also still works with redis as actinia-core requirement. (As long as redis is not replaced with valkey in actinia-core, valkey as dependency is manually needed).