Releases: cloudposse-terraform-components/aws-aurora-postgres
v1.538.2
v1.538.1
v1.538.0
Setting renew @goruha (#34)
## what * Setting renewwhy
- Create merge queue
Summary by CodeRabbit
- Style
- Removed unnecessary blank lines from repository settings configuration.
🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#40)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
chore(deps): update terraform cloudposse/rds-cluster/aws to v1.18.0 @[renovate[bot]](https://github.com/apps/renovate) (#4)
This PR contains the following updates:| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/rds-cluster/aws (source) | module | minor | 1.3.2 -> 1.18.0 |
Release Notes
cloudposse/terraform-aws-rds-cluster (cloudposse/rds-cluster/aws)
v1.18.0
fix: Add perfomance inside to primary cluster @djakielski (#250)
what
- Add performace inside config also on primary cluster
why
- had issues with incompatible cluster and instance parameter
- you can enable performance inside on cluster
references
v1.17.0
fix: reserved instances, aurora rds specifics @oycyc (#249)
what
RDS Reserved Instances multi AZ mode is never available for Aurora engines, see images on the console - this PR checks to ensure that it is set to false if the engine is Aurora:
why
That configuration isn't really applicable anyways since this statement from the AWS docs https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithReservedDBInstances.html:
references
v1.16.0
fix: reserved instance multi_az setting @oycyc (#248)
what
Using local.is_regional_cluster to determine whether or not it is Multi-AZ is not accurate. local.is_regional_cluster only checks if var.cluster_type == "regional", which determines if this is a regional vs global cluster
I could have a regional cluster, but it is NOT multi-az. One determining factor is how many instances in the cluster, if ever more than 1 in a single cluster, then it has to be in multiple AZs. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html
why
If I have a regional cluster, this thinks that it's ALWAYS multi-az, which is not true.
references
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html
v1.15.1
🚀 Enhancements
fix: reserved instances restrictions @oycyc (#244)
what
This conditional check on whether or not to enable reserved instances is too restrictive. contains(["mysql", "postgresql"], local.reserved_instance_engine) is saying that only allow it if it is MySQL or PostgreSQL.
I think contains was originally meant to be like in the literal sense of "contains". Since in my case, I'm using aurora-postgresql, and it fails this check, yet it is one of the options for reserved instances.
why
endswith might be better, but it is TOO restrictive, seeing that there's so many options.
Additionally, Terraform will fail if user specifies the wrong engine type. There's no need for this check.
references
🐛 Bug Fixes
fix: reserved instances restrictions @oycyc (#244)
what
This conditional check on whether or not to enable reserved instances is too restrictive. contains(["mysql", "postgresql"], local.reserved_instance_engine) is saying that only allow it if it is MySQL or PostgreSQL.
I think contains was originally meant to be like in the literal sense of "contains". Since in my case, I'm using aurora-postgresql, and it fails this check, yet it is one of the options for reserved instances.
why
endswith might be better, but it is TOO restrictive, seeing that there's so many options.
Additionally, Terraform will fail if user specifies the wrong engine type. There's no need for this check.
references
v1.15.0
🚀 Enhancements
- Implement and close #237 (add option for local write forwarding) Thank you @Junaid-Tem
- Implement and close #239 (allow the configuration of
reservation_idforaws_rds_reserved_instance) Thank you @oycyc
🐛 Bug Fixes
Multiple cleanu...
Contributors
Assets 2
v1.537.0
fix: update legacy splat operator @RoseSecurity (#23)
## what- Updated the syntax for accessing elements in a list from
data.aws_iam_policy_document.kms_key_rds.*.jsontodata.aws_iam_policy_document.kms_key_rds[*].json.
why
- Enhance code consistency by addressing TFLint errors
*.(splat operator) is an older syntax that returns a list but is not always well-typed. The newer explicit splat syntax is more consistent and predictable when accessing lists
references
Summary by CodeRabbit
- Chores
- Refined internal configuration handling to align with current Terraform standards.
- The update enhances code maintainability without altering any user-visible functionality.
Contributors
Assets 2
v1.536.1
Added tests @goruha (#20)
## what * Added testsSummary by CodeRabbit
-
New Features
- Introduced dynamic selection of network subnets based on accessibility.
- Added new configuration files to enhance infrastructure management for VPC, DNS, and Aurora PostgreSQL deployments (basic, serverless, and disabled).
- Expanded CLI and vendor management configurations.
-
Chores
- Updated scaling parameters for Aurora PostgreSQL.
- Upgraded module versions and refined dependency management.
- Streamlined file tracking by revising ignore rules and removing an obsolete test script.
- Added
.cacheto.gitignoreto prevent tracking of cache files.
-
Tests
- Added a comprehensive test suite validating various deployment scenarios.
🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#22)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
Contributors
Assets 2
v1.536.0
fix: Replace deprecated splat expression with [*] for Terraform 1.5.6… @sushmithakumar (#19)
## Terraform 0.12.0+ Splat Operator Updates ## What Updated Terraform configuration to replace legacy splat syntax(resource.*.attribute)
with modern bracket-based expressions (resource[*].attribute).
Incorporated for expressions where applicable to improve flexibility and readability.
No functional changes to infrastructure; these updates are syntax improvements.
Why
Aligns with Terraform 0.12.0+ enhancements and first-class expression support.
Improves readability and maintainability of Terraform code.
Prevents potential deprecation warnings by replacing outdated syntax.
References
Terraform v0.12.0 Upgrade Guide
Summary by CodeRabbit
Summary by CodeRabbit
- Chores
- Updated the method of constructing identifiers for IAM policy documents to ensure correct value retrieval and formatting.
