Skip to content

Conversation

@MoonMoon1919
Copy link
Contributor

@MoonMoon1919 MoonMoon1919 commented Jun 30, 2018

What it is

Adds engine_version argument to the aws_elasticache_replication_group module.

Why

Previously when referencing this module in an external terraform template any attempt to override the engine version was ignored because this option was unavailable. This resulted in AWS utilizing the default Redis engine (4.0), if attempting to make a cluster utilizing an older version of Redis (ex: 3.2.4) and referencing a parameter group using the family redis3.2 Terraform returns an error stating Error creating Elasticache Replication Group: InvalidParameterCombination: Expected a parameter group of family redis4.0 but found one of family redis3.2.

How I tested

Referenced this branch as the source of the module and used the variable engine_version to set to my desired engine version, spun up a cluster.

sarkis
sarkis previously approved these changes Jun 30, 2018
Copy link

@sarkis sarkis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Thanks again for the PR! Looks like the variable was there but not being referenced anywhere prior to this fix.

This is the newest available engine version available for Redis Elasticache.
Copy link

@sarkis sarkis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After discussion on this, decided it's best to default to the redis4.0 family and latest version of 4.x for engine_version.

@sarkis sarkis merged commit cd1b042 into master Jun 30, 2018
@sarkis sarkis deleted the feature/optional-engine-version branch June 30, 2018 20:55
@sarkis
Copy link

sarkis commented Jun 30, 2018

@osterman
Copy link
Member

Thanks guys!

Copy link

@easyawslearn easyawslearn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catchup,thanks for update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants