v1.13.0

Output instance endpoints, add attributes to `random_pet` that force a new instance @finchr (#236)

…new instance

what

• output instance endpoints
• add aws_rds_cluster_instance attributes that force a new instance to the randmon_pet resource.

why

• I need the actual instance endpoints for the Datadog DMS integration, the default dashboards work better with the exact instance identifier.
• Currently if any of these attributes change (db_subnet_group_name, engine) it will bypass the random_pet and attempt to create instances with the same identifier.

references

v1.12.0

bug/193-enable-http-endpoint @tsaucier0 (#234)

## what * Support for serverless v2 to ensure that configurations (like HTTP endpoints for the Data API) are correctly enabled on instances using the serverless v2 implementation. * A new condition, is_serverless_v2, was introduced to identify serverless v2 instances based on the specific configuration parameters required for its activation.

why

• The original code was intended to enable_http_endpoint based on whether the database instance was using serverless architecture. With the introduction of serverless v2 for certain database engines, there is a need to update the logic to accommodate these options.

references

Closes #193

v1.11.4

🐛 Bug Fixes

fix(reserved instances): use var.instance_type to determine RI offering instead of optional db_instance_class var @kevcube (#235)

the var `db_instance_class` isn't required, so won't always be available. `instance_type` is required.

v1.11.3

feat: support reserved instances @kevcube (#233)

## questions - do we want to allow customization of the count/size of reserved instances?

🤖 Automatic Updates

Update terratest to '>= 0.46.0' @osterman (#215)

## what - Update terratest `>= 0.46.0`

why

• Support OpenTofu for testing

References

• https://github.com/gruntwork-io/terratest/releases/tag/v0.46.0
• DEV-374 Add opentofu to all our Terragrunt Testing GHA matrix

v1.11.2

Dual stack support @ngoyal16 (#231)

## what

RDS cluster can be run in two network modes - IPV4 or DUAL.
Underlying module already supports this parameter

why

It can be mandatory to enable it to be able to connect from ipv6 only runtimes

references

Closes #175

🤖 Automatic Updates

Migrate new test account @osterman (#232)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @osterman (#229)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#228)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

v1.11.1

🚀 Enhancements

fix: Too long identifier name error @MaxymVlasov (#226)

what

Fix too long identifier name without cluster recreation:

set id_length_limit = 40 for

module "aurora" {
  source  = "cloudposse/rds-cluster/aws"
  version = "1.10.0"
  ...
  id_length_limit = 40
}

will cause such recreation if final module.this.id will be between 40-60 characters

why

https://github.com/cloudposse/terraform-aws-rds-cluster/releases/tag/1.10.0 introduced random_pet, which adds 2 extra words on the top of module.this.id, and that exceed limit of 63 allowed characters for RDS names

╷
│ Error: creating RDS Cluster (company-staging-aurora-payments-ledger-service-aliases) Instance (company-staging-aurora-payments-ledger-service-aliases-promoted-piglet-1): operation error RDS: CreateDBInstance, https response error StatusCode: 400, RequestID: 1979b42f-b1df-4e00-b0ec-d3b629b3002d, api error InvalidParameterValue: Invalid database identifier:  company-staging-aurora-payments-ledger-service-aliases-promoted-piglet-1
│ 
│   with module.aurora_aliases.aws_rds_cluster_instance.default[0],
│   on .terraform/modules/aurora_aliases/main.tf line 261, in resource "aws_rds_cluster_instance" "default":
│  261: resource "aws_rds_cluster_instance" "default" {

This PR limit final identifier to 62-63 chars (depends on count of replica)

references

Fixing #213

🐛 Bug Fixes

fix: Too long identifier name error @MaxymVlasov (#226)

what

Fix too long identifier name without cluster recreation:

set id_length_limit = 40 for

module "aurora" {
  source  = "cloudposse/rds-cluster/aws"
  version = "1.10.0"
  ...
  id_length_limit = 40
}

will cause such recreation if final module.this.id will be between 40-60 characters

why

https://github.com/cloudposse/terraform-aws-rds-cluster/releases/tag/1.10.0 introduced random_pet, which adds 2 extra words on the top of module.this.id, and that exceed limit of 63 allowed characters for RDS names

╷
│ Error: creating RDS Cluster (company-staging-aurora-payments-ledger-service-aliases) Instance (company-staging-aurora-payments-ledger-service-aliases-promoted-piglet-1): operation error RDS: CreateDBInstance, https response error StatusCode: 400, RequestID: 1979b42f-b1df-4e00-b0ec-d3b629b3002d, api error InvalidParameterValue: Invalid database identifier:  company-staging-aurora-payments-ledger-service-aliases-promoted-piglet-1
│ 
│   with module.aurora_aliases.aws_rds_cluster_instance.default[0],
│   on .terraform/modules/aurora_aliases/main.tf line 261, in resource "aws_rds_cluster_instance" "default":
│  261: resource "aws_rds_cluster_instance" "default" {

This PR limit final identifier to 62-63 chars (depends on count of replica)

references

Fixing #213

v1.11.0

feat: manage master credentials in secrets manager @pazaan (#221)

what

Allow to manage master credentials in Secrets Manager

why

Managed secrets are more secure and easy to use.

references

• closes #166
• Duplicate of #218, but that PR looks like it's gone stale. I pushed the same fixes to the original branch as well, in case @salemgolemugoo wanted to push them forward to Pull 218, but that hasn't had any activity either.

v1.10.2

🚀 Enhancements

fix: pass var.db_port to RDS cluster instances @emmanuelchibuogwu (#222)

what

Currently, the var.db_port variable is not passed to both aws_rds_cluster resources.

why

var.db_port is passed to the security group but not the cluster instances, this results to the following cases:

1. setting var.db_port to a value other than the default makes the cluster inaccessible .
2. No way to expose the RDS cluster on a different port

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_cluster.html#port
• closes #120

🐛 Bug Fixes

fix: pass var.db_port to RDS cluster instances @emmanuelchibuogwu (#222)

what

Currently, the var.db_port variable is not passed to both aws_rds_cluster resources.

why

var.db_port is passed to the security group but not the cluster instances, this results to the following cases:

1. setting var.db_port to a value other than the default makes the cluster inaccessible .
2. No way to expose the RDS cluster on a different port

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_cluster.html#port
• closes #120

v1.10.1

🚀 Enhancements

Fix conflicting `restore_to_point_in_time` attributes @ericluria (#217)

what

• Fixes handling of use_latest_restorable_time and restore_to_time while preserving existing default values for backwards compatibility

why

• Original attempt at fixing this (#216) was insufficient

references

• Follow-up to original attempt: #216
• Correctly fixes #163

🐛 Bug Fixes

Fix conflicting `restore_to_point_in_time` attributes @ericluria (#217)

what

• Fixes handling of use_latest_restorable_time and restore_to_time while preserving existing default values for backwards compatibility

why

• Original attempt at fixing this (#216) was insufficient

references

• Follow-up to original attempt: #216
• Correctly fixes #163

v1.10.0

reopen #192 @finchr (#213)

what
I implemented create_before_destroy on the aws_rds_cluster_instance default instances.
Originally in #192 but that was closed for reasons we won't go into here.

why
Making a change to any parameter that triggers a replace on a aws_rds_cluster_instance results in all instances being destroyed before attempting to create a new instance which causes an outage. This a faster (and safer) altenative to #191

references
This closes #190 and is an alternative to #191