feat: Add customizable instance settings #132
Closed
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.
Description
Inspired by #119. Added with readme, example and requested changes.
Allow setting individual parameters for cluster instances
Motivation and Context
We needed to add additional read only replica, for reporting needs. Some small instance type was enough for this task, however module allows only to specify number of nodes which share same parameters. We also needed to customize instance name and failover priority - promotion_tier (we do not want to failover to small instance).
Breaking Changes
Requires TF >= v0.12
It is 100% compatible with previous versions.
If you specify variable in a module call:
Customised setting will be used if they are set. If settings are missing module will generate like in previous version name, promotion_tier and will use var.instance_type for all nodes.
How Has This Been Tested?
Tested on our AWS Dev account.
Tested cases: