terraform-aws-rds-cluster

what

• This allows the user to pass in cluster_identifier which will override the autogenerated label id, which is used for other resources

why

• It may be necessary to name the cluster separately from other resources. An example of this could be where you want to uniquely name your database for backup/restore purposes. E.g. you might want to call your database database-1 and then restore to database-2. Being able to pass this in separately will mean you only need to reimport the cluster, it will not want to recreate all other resources as the name you pass in can just be database

what

• Make instance_count independent of autoscaling_min_capacity

why

Fix for https://github.com/cloudposse/terraform-aws-rds-cluster/issues/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.

what

• Bugfix for timeouts

why

• The reference for the dynamic value was wrong

what

• Add the variable copy_tags_to_snapshot

why

• Allow control to copy all Cluster tags to snapshots or not

what

• Adding configurable timeouts for create, update and delete actions

why

• allow to configure timeouts

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

what

• timeout_action added to the aws_rds_cluster resource

why

• timeout_action isn't passed through to the aws_rds_cluster resource when specified at the module level

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

what

• Add RDS Backtrack support

why

• RDS Aurora supports it now

what

• Add global cluster support. Add IAM roles support

why

• New parameters that aws_rds_cluster supports now

what

• Port module to Terraform 0.12
• Pin all providers
• Add example for testing
• Add bats and terratest for the example
• Add Codefresh badge to point to the test pipeline in terraform-modules project
• Update README

why

• Module currently does not work with 0.12. Much easier syntax
• Better regression control
• Automatically test the example on every commit and pull request
• Provision resources on AWS in the test account and check the outputs for the correct values
• terraform-modules project contains pipelines for all terraform modules

what

• Add cluster and reader DNS names

why

• The default DNS names can conflict with other database clusters when deployed together (e.g. DocumentDB for Codefresh on-prem)

what

• Add instance availability zone

why

• Optional parameter to place cluster instance in a specific availability zone, empty will place randomly