Update name of Redis to include v70 #1119
Merged
Conversation
This file contains 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
xlorepdarkhelm
approved these changes
Jun 26, 2024
ccostino
approved these changes
Jun 26, 2024
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.
Changes the name of the Redis instance we are using to an updated name corresponding to a version upgrade. This will unbind the old version and bind the new. This applies to all environments, because they share a single manifest file.
We think this will work without manually using the
cf unbind-serviceandcf bind-servicecommands.I considered undoing PR #1116 because it is a step that should occur after this one. But it appears the deployment pipeline is refusing to apply that PR while the old Redis is still bound, and thus, undoing it in source control is not necessary. It should take effect after this one.