Closed sebastianjanisch closed 4 months ago
Thanks for reporting this issue. First glance, i think we should be able to check the notify-keyspace-events setting and see if it's compatible with what reflex needs for pubsub and if not (and we can't set it ourselves), just raise an error. That way, if there is an alternative config mechanism (like the screenshot), then the user should still be able to run with it, provided they set the correct config manually.
I'm checking with Porter to see how this might be manually configurable (right now I can't edit anything in AWS).
@masenf I updated the parameters manually, see screenshot below. Is there a way to circumvent the error for now?
@sebastianjanisch it does not look possible to bypass the error at this point; but i can throw a PR up for next week's release
Describe the bug When supplying a REDIS url to reflex where the URL points to an AWS ElastiCache instance the backend server fails when it tries to use the CONFIG command which is restricted for AWS ElastiCache.
Exception thrown:
Quick googling I found this thread which explains that the CONFIG command is restricted. https://stackoverflow.com/questions/69656070/facing-redis-problem-unknown-command-config-with-args-beginning-with-set https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/SupportedCommands.html
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen. A graceful handling of the condition that the CONFIG command cannot be used.
Screenshots If applicable, add screenshots to help explain your problem.
Below is the keyspace setup in AWS ElastiCache (maintained by Porter).
Specifics (please complete the following information):
Additional context I'm reaching out to the folks from Porter to see what they can suggest. I presume the config setting still needs to be set but I don't understand enough about Redis.
REF-2978