Upgrade Redis 3 to 4

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Node Redis dependency should be upgraded form 3 to 4, which includes a breaking change, see migration guide.

Feature / Enhancement Description

Upgrade to Redis 4 with Parse Sever 6 release.

Example Use Case

n/a

Alternatives / Workarounds

n/a

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[MobileVet]

@mtrezza Ironically we were just looking at this today as we look to migrate away from Heroku. We had trouble connecting to the Redis instance without TLS (it is on a private network) but it worked fine from outside the network using TLS.

We forced Parse Server to utilize the Node Redis driver 4.4.0 and everything worked just fine on Parse Server 5.2.7. I wonder if there is anything that is actually required to make the update for Parse 6?

[mtrezza]

Great that you already looked into that. I just fixed a conflict in the PR, so we can see whether the CI passes. If it passes, it still would be good if someone could take a look at the migration guide to see whether there is anything relevant for Parse Server. Not sure how good the Redis test coverage in Parse Server is.

For example:

The configuration object passed to createClient has changed significantly with this release. See the client configuration guide for details.

...and indeed, the CI in the PR fails with:

TypeError: Cannot read properties of undefined (reading 'createClient')

[parseplatformorg]

🎉 This change has been released in version 6.0.0-alpha.7

[parse-github-assistant]

The label state:released-alpha cannot be used in combination with state:breaking.

[dblythy]

Reopening as the Redis Live Query publisher was not updated

[parseplatformorg]

🎉 This change has been released in version 6.0.0-alpha.12

[parseplatformorg]

🎉 This change has been released in version 6.0.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 6.0.0