Azure/AWS: Take into account CONFIG command may not work

Hi patch #21 works like a charm with AWS

#21 works for me

Change patch #21

Small fix to patch #21 that gave me this error

Warning: Trying to access array offset on value of type bool in Drupal\redis\Controller\ReportController->overview() (line 176 of modules/contrib/redis/src/Controller/ReportController.php).

watchdog_exception() is deprecated and removed in D11.

Adding a patch compatible with the 1.8 version of the module, deprecating watchdog_exception when possible.

Having the same issue with version 1.7.0 on AWS, the patch #21 is working for me as expected.

Sorry for making more noise. Here's a simplified approach that rely on INFO command instead of CONFIG.

patch #26 worked for me on latest version module, thanks! greetings,

#21 still works like a charm with AWS Redis cache. thanks!

Client Predis
Version 6.2.6
Drupal 9.5.11
Redis 8.x-1.7

Please can the patch at comment #28 please be added to a production release. It is necessary to allow the module to work with Azure Cache for Redis. Tested successfully from Azure App Service with Drupal 10.3.

Thanks for the fix. I can confirm the patch at #28 works for me in an Azure hosted environment with Drupal `v10.4.5` using Redis `v1.9.0` and Predis `v1.1.10`. I would be very interested in seeing it merged so I don't have to manually track this issue anymore.

Patch at #28 works for me with AWS Elasticache-Redis with Drupal 10.4.5, drupal/redis 1.9.0, and predis 2.4.0.

(I also had to apply a patch from Support TLS for Predis ✨ Support TLS for Predis Needs review to enable this module to provide the "tls" scheme to predis and apparently I'm following @mitokens around on this.)

I believe this has been addressed by 📌 Abstract info-collection RedisController to deal with special environments Active , if not, feel free to reopen.

I'm a little doubtful, as 📌 Abstract info-collection RedisController to deal with special environments Active is still calling config() to retrieve the value. I have been running with #28 on a project for a while now, that eliminates that completely. But maybe the condition in there is enough to prevent that from happening.

Yes, but it only calls it if the information isn't already available. stats/info/config output seems to vary wildly between different, it is very much possible that while config() might not work on Azure, info() might not work somewhere else. There also are patches here wit different approaches. if necessary we can extend the logic with a try/catch, removing it completely does not seem like a viable option.

FWIW, I can't reproduce the original problem anymore. 🙃 I had this patch for a site on Platform.sh, maybe they've changed something.

I saw that comment and was surprised, we've been using redis on platform.sh since 2015 and never needed this.

Weird. I looked through my Git history, but no details. Only confirmation that it was for Platform.sh. I do see that the project is on Redis 6.0 and has been since we added Redis. That's not supported anymore, not sure what the status was when it was added.