Add conditional Valkey cache support for Drupal - #478
Open
jacobaaronyeager wants to merge 1 commit into
Open
Conversation
Provision tagged Cloud.gov ElastiCache infrastructure, bind it when available, and configure Drupal Redis/Predis with TLS while preserving cache fallback.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provision tagged Cloud.gov ElastiCache infrastructure, bind it when available, and configure Drupal Redis/Predis with TLS while preserving cache fallback.
Jira ticket
DIGITAL-752
Purpose
Install Redis to reduce cache load on Drupal db
Deployment and testing
QA/Testing instructions
(NOTE: AI suggested testing.)
Before deployment, record the elapsed time from a comparable dev static-site generation run.
Deploy the branch to
devthrough the normal build-and-deploy workflow. Confirm infrastructure completes before the Drupal deployment.Verify the service and binding without exposing credentials:
Confirm digital-gov-cache-dev is bound and its VCAP_SERVICES entry includes the cache-service tag.
The class should be in the Drupal\redis namespace.
Run static generation again with comparable content and record elapsed time. Compare it with the baseline, along with the RDS size and Drupal instance count.
Confirm fallback behavior in a space without digital-gov-cache-: deployment should succeed and Drupal should continue using its normal database cache backend.
Checklist for the Developer
Checklist for the Peer Reviewers