Releases: cloudposse/terraform-aws-rds-cluster
Releases · cloudposse/terraform-aws-rds-cluster
0.27.0
0.26.0
0.25.0 Make `instance_count` independent of `autoscaling_min_capacity`
what
- Make
instance_count
independent ofautoscaling_min_capacity
why
Fix for #63
The cluster_size or the instance_count should be independent of autoscaling_min_capacity as autoscaling_min_capacity is automatically taken care of by AWS through the autoscaling policy.
For example, when autoscaling is enabled:
if I specify:
cluster_size = 2
autoscaling_min_capacity = 1
terraform creates only one instance even though cluster_size is set to 2 ,
and if I specify:
cluster_size = 2
autoscaling_min_capacity = 2
terraform spins up 2 instances but AWS autoscaling policy immediately spins up one more instance, which is not desired.
0.24.1
0.24.0 Bugfix for `timeouts`
what
- Bugfix for
timeouts
why
- The reference for the
dynamic
value was wrong
0.23.0 Allow setting `copy_tags_to_snapshot`
what
- Add the variable
copy_tags_to_snapshot
why
- Allow control to copy all Cluster tags to snapshots or not
0.22.0 Adding timeout for RDS cluster resources
what
- Adding configurable timeouts for create, update and delete actions
why
- allow to configure timeouts
0.21.0 Add ability to specify additional security groups
what
- Add ability to specify additional security groups
why
- In case if need for additional security group IDs to apply to the cluster, in addition to the provisioned default security group with ingress traffic from existing CIDR blocks and existing security groups
0.20.0 Respect timeout_action from scaling_configuration
what
timeout_action
added to theaws_rds_cluster
resource
why
timeout_action
isn't passed through to theaws_rds_cluster
resource when specified at the module level
0.19.0 Use the latest label module to support the `environment` attribute
what
- Use the latest label module to support the
environment
attribute
why
- Allow the
environment
attribute to be passed to included modules - Useful for naming resources