-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_elasticache_replication_group: modify before scale in #34819
aws_elasticache_replication_group: modify before scale in #34819
Conversation
Community NoteVoting for Prioritization
For Submitters
|
When scaling in (i.e. reducing node count), apply change _after_ making other modifications. This avoid an invalid parameter error in certain conditions, e.g. if reducing from 2 to 1 while also disabling multi_az_enabled and/or automatic_failover_enabled, the configuration has to be applied before reducing node count (otherwise an error like 'InvalidParameterValue: Must have at least 1 replica for Multi-AZ enabled Replication Group' is generated To avoid issues in the other direction, continue to apply scale _out_s prior to other modifications
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @chris-peterson 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
When scaling in a
aws_elasticache_replication_group
(i.e. reducing node count), resize after making other modifications.This avoid an invalid parameter error in certain conditions, e.g. if reducing from 2 to 1 while also disabling
multi_az_enabled
and/orautomatic_failover_enabled
, the cluster configuration has to be applied before reducing node count (otherwise results in an error like this):I've left the scale out path alone to avoid issues in the other direction (e.g. enabling
automatic_failover_enabled
while scaling from 1 to 2)