From 1a92d1583e5408a30d29475224d5f43c3ce31be4 Mon Sep 17 00:00:00 2001
From: Logan Davis <logankeahidavis@gmail.com>
Date: Thu, 30 Jan 2020 16:17:31 -0800
Subject: [PATCH] feat(encryption): support rediss:// connection strings

Previously, combee would fail to connect when given a rediss://
connection string for a TLS-enabled instance. This commit adds
support for such connection strings. Support for these has apparently
not yet been released upstream to the redis npm module.
https://github.com/NodeRedis/node_redis/issues/1484
---
 repl.js | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/repl.js b/repl.js
index 87248cf..0ed06ec 100755
--- a/repl.js
+++ b/repl.js
@@ -23,7 +23,17 @@ class Combee {
     assert(config.redisUrl, 'must provide redis URL');
     assert(config.queues || config.queuePrefix, 'must provide queues');
 
-    this.redis = redis.createClient(config.redisUrl);
+    let redisConnection = config.redisUrl;
+    if (config.redisUrl.startsWith('rediss:')) {
+      // A rediss:// URL means in-transit encryption is enabled for the redis host, so use TLS.
+      redisConnection = {
+        url: redisConnection.replace('rediss:', 'redis:'),
+        tls: {},
+      };
+    };
+
+    this.redis = redis.createClient(redisConnection);
+
     this.redis.on('error', function(err) {
       console.log(err);
     });