Fix Redis to Valkey in-place upgrade by handling Engine in ModifyReplicationGroup #188
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.
Fixes: aws-controllers-k8s/community#2299
Description of changes:
fixes the issue where in-place upgrades from ElastiCache Redis to Valkey clusters failed with
InvalidParameterCombination: valkey parameter group is not applicable to engine redis
. The problem occurred because the ElastiCache controller's customModifyReplicationGroup
implementation was missing theEngine
andCacheParameterGroupName
fields in the API request payload, causing AWS to reject Valkey parameter groups being applied to what it perceived as a Redis engine. Additionally, theModifyReplicationGroup
API returns stale field values that don't immediately reflect requested changes, leading the controller to detect false differences and trigger terminal conditions. The solution adds both missing fields to the modify request payload, and normalizes API responses by overriding stale Engine field values with the user's intended values before processing.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.