Allow to pass ssl option for sentinel with params

[IevaGraz]

Hi,

We do not use url param with sentinel config and rather pass host, port, ssl options ourselves. After #277 the ssl config passed with params is deleted - would it be OK to keep that param and support both parsing from url and direct setting of ssl param?

We are getting No sentinels available when trying to use SSL connection and the param was removed from sentinel connection configs. This is because we use SSL both for master/replica communication AND sentinel communication

[stanhu]

Oops, I had assumed that ssl wasn't passed here, but I missed the merge(client_config):

        client_config = {
          username: url_config.username,
          password: url_config.password,
          db: url_config.db,
          ssl: url_config.ssl?,
        }.compact.merge(client_config)

Perhaps what should happen is the ssl gets set if it isn't set already?

[IevaGraz]

@stanhu I wonder how people use it. In our case, if we have SSL enabled, it is enabled for all connections. Easiest fix would be to just remove that delete and set the same option. But I'm not sure if that won't break your use case? More complex would be to separate connection and sentinel connection ssl configs.

[stanhu]

#280 might be a better fix.