Rspamd: update history key in Redis configuration #3927
Merged
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.
Description
Pinning the Rspamd is not something I want to do for now. DMS will ship 3.8.4 on
:edge
.This change alters the Redis history key to not have the hostname, which easily changes in Kubernetes, in the Redis history key to keep the Redis history across pod restarts. This is a breaking change, as the Redis history might (and very likely will) be lost when upgrading.
Fixes #3922
Type of change
Checklist
docs/
)CHANGELOG.md