Adds TLS redis configuration support for encryption-at-rest enabled redis instances

[validkeys]

What Changed & Why

For my deploy process I'm tunnelling through an EC2 instance to an elasticache redis cluster with encryption-at-rest enabled. In order to connect to ssl redis instances, i need to be able to specify the tls configuration options for ioredis.

PR Checklist

• Add tests
• Add documentation
• Prefix documentation-only commits with [DOC]

[validkeys]

The failed test above is due to yarn and node 4 having a conflict about "let". Appears unrelated to my code

[lukemelia]

Looks good to me. 👍

[ghedamat]

@validkeys sorry for being so late here,
do you have a sec to look at the fail (even though is unrelated to your code?) if not I can tryt o make some time later this week

thanks again!

[dadamschi]

@validkeys FWIW was not working for azure-redis using port 6380 or non-default port.

We forked https://github.com/validkeys/ember-cli-deploy-redis, updated ioredis to ^4.15.1 and added support for rediss and it works on port 6380.

@ghedamat @lukemelia

[lukemelia]

@dadamschi @validkeys FYI, I've now upgraded this addon to the most recent ioredis release. If either of you are interested in adding TLS configuration support, feel free to revive this PR or open a new one.

[nbibler]

My understanding of ioredis seems to be that if the URL uses the rediss:// protocol, it will automatically setup and use TLS. If that's correct, then seemingly we can modify the Regex to allow for the additional s here:

ember-cli-deploy-redis/index.js

Lines 74 to 78 in aba1873

	var redisUrlRegexp = new RegExp('^redis://');
	if (!this.pluginConfig.url.match(redisUrlRegexp)) {
	throw new Error(`Your Redis URL appears to be missing the "redis://" protocol. Update your URL to: redis://${this.pluginConfig.url}`);
	}

And that should pass through the desire to use a TLS connection to ioredis, right?

[lukemelia]

I believe all the intended functionality of this PR has now been incorporated.