v0.27.0

fix: use correct variable with route53-cluster-hostname @syphernl (#83)

what

• Use dns_name instead of name while using the route53-cluster-hostname module.

why

• The name parameter is not being used by the route53-cluster-hostname module invocation and results it falling back to the value of module.this.id rather than the default value of db for host_name within the terraform-aws-rds module.

references

• https://github.com/cloudposse/terraform-aws-route53-cluster-hostname/blob/master/main.tf#L3

v0.26.0

Terraform 0.14 upgrade @maximmi (#81)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

0.25.0 Bump terraform-aws-route53-cluster-hostname

what

• Bump module dns_host_name from 0.5.0 to 0.7.0

why

• terraform-aws-rds claims to support provider AWS >= 2.0
• terraform-aws-route53-cluster-hostname supports AWS ~> 2.0
• By bumping terraform-aws-route53-cluster-hostname to a version supporting AWS >= 2.0 we ensure that this RDS module's dependencies don't imply unexpected restrictions.
• terraform-aws-route53-cluster-hostname 0.6.0 would also be valid; but 0.7.0 causes no breaking changes, so it makes sense to skip ahead to the latest valid version.

0.24.0 update aws provider version

what

• Update aws provider to >= 2.0 avoid module version conflicts when used with >= 3.0 modules (eg. aws-eks-node-group).

why

• This module is being used with terraform-aws-eks-node-group which needs aws provider version to be >= 2.0 to fix version conflicts.

references

• See cloudposse/terraform-aws-eks-node-group#41 for details. This tackles one of the modules causing the issue.

0.23.0 Support `monitoring_role_arn` which is required for `monitoring_interval`

what

• Add monitoring_role_arn input variable which gets passed through to aws_db_instance resource

why

• without this, when using monitoring_interval, you get the following error:

InvalidParameterCombination: A MonitoringRoleARN value is required if you specify a MonitoringInterval value other than 0.

references

• this is already supported by cloudposse/terraform-aws-rds-cluster

0.22.0 Additional TF 0.13.0 changes

what

• upgrade cloudposse/terraform-aws-route-53-cluster-hostname to 0.5.0

why

• for TF 0.13.0 support

references

• https://github.com/cloudposse/terraform-aws-route53-cluster-hostname/releases/tag/0.5.0

0.21.1: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#65)

## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

Co-authored-by: Erik Osterman <[email protected]>

0.21.0

[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.20.0: Add IAM Authentication (#62)

* add iam authentication

* Updated README.md

* Executed 'terraform fmt'

Co-authored-by: actions-bot <[email protected]>

0.9.4 Add ARN output

what

• Add the ARN of the RDS cluster as an output

why

• Due to some weirdness in the API, you can't make read replicas in different subnet groups without using the ARN. See referenced issue.
• Also seems pretty inconsistent to not provide the ARN as an output.

References

• Using ARN workaround found here: hashicorp/terraform-provider-aws#528