Add TLS profiles for easier configuration

[GertSallaerts]

Inspired by seeing this in MySQL libraries (mysql and mysql2), this PR adds support for specifying a TLS profile that takes care of configuring for example redis.com's certificate authority.

[luin]

Thanks for the PR!

I subscribed to the flex plan and created a database. However, when I wanted to connect to it with the following code:

const client = new Redis({
  host: "redis-xxx.us-east-1-mz.ec2.cloud.rlrcp.com",
  password: "xxxxxx",
  port: 13342,
  tls: 'RedisCloudFlexible',
});

I got the following error:

Error: unable to get issuer certificate

Did I miss anything?

[GertSallaerts]

I'm afraid I only have access to the fixed plan right now and can't reproduce your error on our databases on there. Looks like the flex plans are charged monthly, otherwise I'd make a quick test subscription myself 😅

[GertSallaerts]

@luin I've been in contact with Redis.com and got a flexible suscription to test with. Turns out the flexible CA from their site was missing a part of the certificate chain. They've sent me the correct CA now and I've updated the PR with it. On my own flexible subscription it is working fine now.

[luin]

Awesome! Thanks for the contribution 🥳

[ioredis-robot]

🎉 This PR is included in version 4.28.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[silentroach]

but why?

looks like it is a bad idea to store certificates inside package, to maintain it and make the certificate list dependant on package version