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

databroker: remove redis storage backend #4699

Merged
merged 5 commits into from Nov 2, 2023

Conversation

kenjenkins
Copy link
Contributor

Summary

Remove the Redis databroker backend. According to
https://www.pomerium.com/docs/internals/data-storage#redis it has been discouraged since Pomerium v0.18.

Related issues

User Explanation

Remove the Redis databroker backend.

Checklist

  • reference any related issues
  • updated docs
  • updated unit tests
  • updated UPGRADING.md
  • add appropriate tag (improvement / bug / etc)
  • ready for review

Remove the Redis databroker backend. According to
https://www.pomerium.com/docs/internals/data-storage#redis it has been
discouraged since Pomerium v0.18.
@kenjenkins kenjenkins added the docs Docs update required label Nov 1, 2023
@coveralls
Copy link

coveralls commented Nov 1, 2023

Coverage Status

coverage: 63.701% (-0.4%) from 64.112% when pulling 20c4098 on kenjenkins/remove-redis-backend into 0b79a28 on main.

@kenjenkins kenjenkins marked this pull request as ready for review November 2, 2023 15:46
@kenjenkins kenjenkins requested a review from a team as a code owner November 2, 2023 15:46
@kenjenkins kenjenkins merged commit 4f648e9 into main Nov 2, 2023
9 checks passed
@kenjenkins kenjenkins deleted the kenjenkins/remove-redis-backend branch November 2, 2023 18:53
@kenjenkins kenjenkins added the breaking Backward incompatible change in behaviour, api or config label Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Backward incompatible change in behaviour, api or config docs Docs update required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants