update drupal redis patch links

[scottbuscemi]

Summary

https://www.drupal.org/project/redis/releases/8.x-1.10

The latest version of the Redis module fixes an issue that we were previously suggesting a patch for.

[pantheon-decoupled]

⚡ Deployed with Pantheon Decoupled

This build was successfully deployed with Pantheon. You can track the build logs here.

👀 Preview: https://pr-9635-documentation.appa.pantheon.site
🛠️ Manage in Pantheon: https://dashboard.pantheon.io/site/2b30153f-e8b1-4427-b076-6109e704ba5d/overview

[lcatlett]

A few things folks should be aware of:

• This shouldn't be merged until the settings snippets are updated to account for new settings like https://git.drupalcode.org/project/redis/-/commit/ff3890a4da59101d0d59507979a22a017e5a7d66#e81e5be2706877eff882fb5ee8272aa85817cdac_41_42.

• This release is not just the patch that has now been tested extensively on Pantheon. There are changes to recommended defaults such as eviction policy that have never been tested with any customer set up. A significant example is volatile-lfu is now the recommended default eviction policy, so that's going to either need platform changes, or additional work in the form of a custom module to enforce.

• Eviction policy is one example but there are multiple critical changes that need to be tested both on setting up redis for the first time on a site, and upgrading existing sites to use these new capabilities / recs

• the above needs to be coordinated with the d11 roadmap for cache enhancements. Settings like $settings['cache_preload_tags'] are not compatible with the Drupal redis module currently https://www.drupal.org/node/3505248

[stevector]

Looks like we should address @lcatlett comments before merging #9635 (comment)

[stevector]

@scottbuscemi, can you respond?

[scottbuscemi]

@lcatlett Does anything you brought up affect this PR? Are you advocating for customers to not use the latest redis module release on Pantheon? I'm not understanding.

[lcatlett]

@lcatlett Does anything you brought up affect this PR? Are you advocating for customers to not use the latest redis module release on Pantheon? I'm not understanding.

@scottbuscemi To clarify: I'm not saying customers shouldn't use the latest Redis module release. I'm saying this PR, as written, could inadvertently guide customers into configurations that haven't been validated on Pantheon yet.

The issue is that the 8.x-1.10 release bundles more than just the patch fix. It also changes recommended defaults and introduces new settings. If we update the docs to point to this release without also updating the settings snippets, customers following our documentation could end up with:

• Eviction policy mismatches (volatile-lfu vs what the platform expects)
• Missing or incorrect settings that the new module version now requires
• Conflicts with upcoming D11 cache enhancements

When we publish configuration in our docs, customers reasonably assume it has been validated on Pantheon. That's the implicit contract of official documentation. So if we're going to point to this new release, the settings snippets also need to be updated to reflect tested, Pantheon-validated configurations for it.

So yes, this affects the PR directly. The doc changes need to be paired with updated settings snippets that account for the new module's requirements. Otherwise we're telling customers "use this new version" without giving them the correct configuration to go with it.

[lcatlett]

An update: The D11 issues are more severe than I realized and redis cannot be used at all as a backend for D11 until critical regressions are fixed in the redis module AND the default settings.php config in Pantheon docs are updated. This impacts any Drupal 11 site attempting to use redis, not just sites on Pantheon. Sites that update to D11 without fixes will immediately WSOD and there is no workaround that can be deployed via settings.php to resolve this.

I filed an issue on behalf of Pantheon: https://www.drupal.org/project/redis/issues/3564915