-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[Feature]: Support for connecting via TLS to a managed Redis database #26723
Comments
Another user requested this feature. |
I am encountering an issue with connecting Redis to Appsmith due to the inability to configure the TLS protocol. This is a significant blocker for our current development, which heavily relies on the Redis plugin in Appsmith. Could you please provide any support or updates on this issue? Resolving this would greatly assist our ongoing projects. Thank you for your help. |
@Abhay-011 could you tell us a bit about your use case? We're currently help up with multiple feature requests and I'm not sure when we will get to this. One suggestion I have would be to write an API for the redis datasource and have Appsmith integrate with that API |
I have same problem here. I need to connect a redis with TLS enabled. |
HI @Nikhil-Nandagopal, I am willing to work on this. |
@AnnaHariprasad5123 please go ahead. Let us know if you need any clarifications/designs etc. |
Hi @Nilansh Bansal, Good morning. For Redis-tls, Is this design ok? |
@AnnaHariprasad5123 I believe there would be some changes to the UI design as per Appsmith's UI/UX guidelines. I can confirm this with our product designer @carinanfonseca and let you know but until then you can proceed with the above design similar to one of redis-insight and add the functional code. We will share you the updated designs in a few days until then you can work on the functionality and raise a PR. cc: @rohan-arthur @carinanfonseca @appsmithorg/query-js-pod |
Hey @AnnaHariprasad5123 can you commit the UI changes in a draft PR? We want to generate a DP on the same and get it reviewed by @carinanfonseca. |
Hi @NilanshBansal, Could you check that. |
@carinanfonseca here is the DP with the UI changes. Can you please verify the designs here 🙏 |
@AnnaHariprasad5123, first of all, thank you so much for your contribution. The experience you implemented aligns well with what we have in other data sources, so we should move forward with it. |
Hi @NilanshBansal, Could you check the pr. |
…github.com:AnnaHariprasad5123/appsmith into chore/external-contribution-37106
…github.com:AnnaHariprasad5123/appsmith into chore/external-contribution-37106
…github.com:AnnaHariprasad5123/appsmith into chore/external-contribution-37106
…github.com:AnnaHariprasad5123/appsmith into chore/external-contribution-37106
Is there an existing issue for this?
Summary
The Appsmith Redis plugin currently allows you to connect to Redis instances that do not require the TLS protocol. For cases where it is explicitly necessary to connect via TLS, the plugin does not allow the connection and generates an error message saying
Unexpected end of stream
.Why should this be worked on?
It is important that this new feature is worked on, since there are currently services like DigitalOcean that require connection through TLS to access resources like Database Clusters. In this case, the official DigitalOcean documentation specifies that to connect remotely to a managed Redis database, it is necessary to do so using TLS.
The text was updated successfully, but these errors were encountered: