[5.7] support change redis sentinel connection to default without change version control file database.php in some production environment

[dynamohuang]

Enable Define default connection so that support redis sentinel connection without change version control file database.php in some production environment. In this way Just change .env REDIS_DEFAULT_CONNECTION.

For eg:

'default_connection' => env('REDIS_DEFAULT_CONNECTION', 'default'), 'default' => [ 'host' => env('REDIS_HOST', '127.0.0.1'), 'password' => env('REDIS_PASSWORD', null), 'port' => env('REDIS_PORT', 6379), 'database' => 0, ], 'sentinel' => [ 'tcp://192.168.104.65:26379?timeout=0.100', 'tcp://192.168.104.65:26380?timeout=0.100', 'options' => [ 'replication' => 'sentinel', 'service' => 'clouds', 'parameters' => [ 'password' => 'clouds@1234', 'database' => 0, ], ], ],

[dynamohuang]

Referring issue:
#18850

[dynamohuang]

In database config file
// Create a custom connection to use redis sentinel 'cache_sentinel' => [ // Set the Sentinel Host from Environment (optinal you can hardcode if want to use in prod only) env('CACHE_REDIS_SENTINEL_1'), env('CACHE_REDIS_SENTINEL_2'), env('CACHE_REDIS_SENTINEL_3'), 'options' => [ 'replication' => 'sentinel', 'service' => 'cachemaster'), 'parameters' => [ 'password' => env('REDIS_PASSWORD', null), 'database' => 0, ], ], ],
https://stackoverflow.com/questions/52885098/configure-redis-sentinel-in-laravel-5-5

[taylorotwell]

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.

Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.

Thanks!