Consolidate Redis and Valkey Best Practices Recommendations and updating the configurations

[rimomcosta]

Purpose of this pull request

This pull request consolidates the Redis and Valkey best practices recommendations into a single implementation playbook topic and updates the related configuration guidance.

It also removes the redundant standalone Redis and Valkey planning articles and updates the TOC, planning overview, redirects, and What's New references so navigation and existing links resolve to the consolidated topic.

Affected pages

• https://experienceleague.adobe.com/docs/commerce-operations/implementation-playbook/best-practices/planning/redis-valkey-service-configuration.html
• https://experienceleague.adobe.com/docs/commerce-operations/implementation-playbook/best-practices/planning/overview.html
• https://experienceleague.adobe.com/docs/commerce-operations/operational-guides/home.html#whats-new

Additional information

Related PR against Commerce on Cloud Guide: Remove outdated warning on REDIS and VALKEY cache configuration options

What's New highlights

whatsnew
Updated the best practices for Redis and Valkey configuration and provides related configuration guidance.

[prateek-karanpuria-adobe]

While re-reviewing the merged document, I noticed that some Valkey-specific references from the original Valkey document were not included in the consolidated version. To fully preserve content from both Redis and Valkey documents, a few updates are needed in the following sections:

1. Configure Redis L2 cache section

   • Currently references REDIS_BACKEND.
   • The Valkey equivalent VALKEY_BACKEND should also be mentioned for Valkey deployments.

2. Enable Redis slave connection section

   • Currently documents REDIS_USE_SLAVE_CONNECTION.
   • The Valkey equivalent VALKEY_USE_SLAVE_CONNECTION should also be included.

3. Additional information section

   • Only Redis documentation links are referenced.
   • Valkey documentation links (valkey-pg-cache, valkey-session) should also be added.

4. Deployment log example in the Redis session separation section

   • The example currently references:
     • service 'redis'
     • service 'redis-session'
   • A corresponding Valkey example (valkey, valkey-session) should also be included.

Because of these omissions, the combine document does not yet fully preserve all information from both the Redis and Valkey original files.

[rimomcosta]

While re-reviewing the merged document, I noticed that some Valkey-specific references from the original Valkey document were not included in the consolidated version. To fully preserve content from both Redis and Valkey documents, a few updates are needed in the following sections:

1. Configure Redis L2 cache section

   • Currently references REDIS_BACKEND.
   • The Valkey equivalent VALKEY_BACKEND should also be mentioned for Valkey deployments.

2. Enable Redis slave connection section

   • Currently documents REDIS_USE_SLAVE_CONNECTION.
   • The Valkey equivalent VALKEY_USE_SLAVE_CONNECTION should also be included.

3. Additional information section

   • Only Redis documentation links are referenced.
   • Valkey documentation links (valkey-pg-cache, valkey-session) should also be added.

4. Deployment log example in the Redis session separation section

   • The example currently references:

     • service 'redis'
     • service 'redis-session'

   • A corresponding Valkey example (valkey, valkey-session) should also be included.

Because of these omissions, the combine document does not yet fully preserve all information from both the Redis and Valkey original files.

All those points are referenced:
1:

2:

3:
"Only Redis documentation links are referenced" - The original document also misses this, so this is out of scope of this merge.
"Valkey documentation links (valkey-pg-cache) should also be added." - Again, out of scope, it also is missing in the original document.
"valkey-session" - This is also well documented here:

4:
valkey is fully covered in the examples as well:

The current documentation is not just a combination, it fixes several errors from the original documentation and goes even beyond.

Please check again.

Regards

[rimomcosta]

Hi Reviewers,

Please refrain from using AI for this review. Those configurations are way too specific and one of the most sensitive for the merchant's environment.

Also, please add the comments in line, example:

Thank you a lot,
Regards,

[prateek-karanpuria-adobe]

@rimomcosta - Thanks for the detailed look at the PR comment. However, I do see some important links about valkey-pg-cache already present in the original document as well. Could you please have a look and do the needful? Thanks.

[meker12]

This PR has been imported to the enterprise repo. Any further updates need to be made in the imported PR.

[dshevtsov]

Addressed in c96e5b3.