what

Add option for enabling global write forwarding for aws rds cluster.

why

• Ability to enable global write forwarding across our aws rds clusters.
• https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding-apg.html
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_cluster#enable_global_write_forwarding

Bumps google.golang.org/grpc from 1.51.0 to 1.56.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

what

• Install a repository config (.github/settings.yaml)

why

• Programmatically manage GitHub repo settings

what

• Install a .github/settings.yaml

why

• Programmatically manage GitHub repo settings

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

what

• Reran make readme to rebuild README.md from README.yaml
• Migrate to square badges
• Add scaffolding for repo settings and Mergify

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

This PR contains the following updates:

Release Notes

what

Implement a simple rolling update for the aws_rds_cluster_instance default instances.

why

To implement a zero downtime deploy for simple changes.

references

closes #190

what

Use existing storage_type variable for global DBs, too. Currently, it is only set for regional clusters.

why

Aurora clusters offer two different storage types, standard and I/O-Optimized. Which one is employed for clusters in a global DB should be configurable to be able to realize cost savings that I/O-Optimized offers for certain workloads.

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_cluster#storage_type
• https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBCluster.html
• https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.StorageReliability.html#aurora-storage-type

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

what

Add missing config to aws_rds_cluster.secondary

why

Error: creating RDS Cluster (<redacted>) Instance (<redacted>): InvalidDBClusterStateFault: Set the Serverless v2 scaling configuration on the parent DB cluster before creating a Serverless v2 DB instance.
│       status code: 400, request id:

Tested on my cluster and confirmed to work when a serverless configuration is provided.

what

• Add parameter_group_name_prefix_enabled variable (defaults to true to maintain the current functionality)
• Allow using both the name and name_prefix attributes in aws_rds_cluster_parameter_group and aws_db_parameter_group resources
• Update tests to the latest versions
• Update examples to use the corerct combinations of DB instance classes and DB engine versions

why

• Allow updating old Aurora clusters, which were provisioned with the old versions of the module, to the latest version of the module without rebooting the DB instances. Old clusters, provisioned with the old versions of the module, use the name attribute (which was the only option in the old versions of the module) instead of name_prefix attribute
• Updating the parameter group causes the DB instance to reboot, which could cause a downtime. Depending on the size of the database, the downtime could take some amount of time not suitable for production clusters (after reboot, the database will go through all the recovery points and logs, and depending on the database size, it could take some time)

When you associate a new DB parameter group with a DB instance, 
the modified static and dynamic parameters are applied only after the DB instance is rebooted. 
However, if you modify dynamic parameters in the DB parameter group after you associate it with the DB instance, 
these changes are applied immediately without a reboot.

references

• https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html

what

Support AWS Provider V5 Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Rebuild github dir from the template

what

• Allow to create Activity Stream for RDS Cluster

Added by @nuru:

• Move PostgreSQL testing to proper test region (us-east-2)
• Fix expected subnet CIDR due to fewer availability zones in us-east-2 than us-east-1
• Increase test parallelism so that tests complete in under 60 minutes

why

• Can be used to enable and activity stream from the cluster module itself

what

• For a multi a-z rds cluster skip creating aws_rds_cluster_instance resource when engine type is NOT aurora, aurora-mysql, aurora-postgresql
• AWS provider has a bug that is causing the terraform apply to fail due to a missing rebooting state. I have a PR merged with terraform-aws-provider that fixes it and will be included in the next release 4.23.0.
  • https://github.com/hashicorp/terraform-provider-aws/pull/25718

why

• Prevent terraform from crashing when creating a non-aurora multi a-z cluster.
• aws provider update for fixing rebooting state when creating multi a-z cluster.

references

• closes https://github.com/cloudposse/terraform-aws-rds-cluster/issues/148
• https://github.com/hashicorp/terraform-provider-aws/pull/25718

what

• Pass a value to db_instance_parameter_group_name argument when allow_major_version_upgrade is true.

why

• When absent, the upgrade process would fail with InvalidParameterCombination exception thrown from AWS provider.

references

• closes #134
• Terraform aws_rds_cluster resource documentation

what

• Adding missing required db_cluster_instance_class variable when creating a provisioned multi a-z rds cluster.

why

• Prevent failure when doing a terraform apply to create the multi a-z rds cluster.

references

• Closes https://github.com/cloudposse/terraform-aws-rds-cluster/issues/146