feat: Allow to customizable instance settings #146
Merged
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
Extend PR #132 to allow publicly setting can be set per instance
Motivation and Context
Sometimes cluster instances can be hidden from public access (let's say writer is private but readers are not), I've combined changes from PR #132 and extend them to control publicly_accessible setting per instance.
Breaking Changes
Doesn't change current setup, old configuration syntax still supported.
How Has This Been Tested?
This code from provided example works:
instances_parameters = [ // List index should be equal to
replica_count// Omitted keys replaced by module defaults { instance_type = "db.r5.2xlarge" publicly_accessible = true }, { instance_type = "db.r5.2xlarge" }, { instance_name = "reporting" instance_type = "db.r5.large" instance_promotion_tier = 15 } ]