Skip to content

WIP: initial work on redis cache container - #125

Open
code-forger wants to merge 1 commit into
feat/rsc-persistent-cache-tagsfrom
feat/rsc-redis-connection
Open

code-forger wants to merge 1 commit into
feat/rsc-persistent-cache-tagsfrom
feat/rsc-redis-connection

Conversation

@code-forger

Copy link
Copy Markdown
Member

PR Raised for discussion only, there are no tests, and concerns like intentionally disconnecting from redis do not exist.

Description

Allow the caller to connect the cache to redis

Motivation and Context

This allows the caller to opt into a more persistent cache, if they deployment contains multiple servers

How Has This Been Tested?

N/A

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (adding or updating documentation)
  • Dependency update

Checklist:

  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • My changes are in sync with the code style of this project.
  • There aren't any other open Pull Requests for the same issue/update.
  • These changes should be applied to a maintenance branch.
  • [] I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using Fetchye?

@code-forger
code-forger added this pull request to stack #123 September 28, 2026 09:33
@code-forger
code-forger requested review from a team as code owners September 28, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant