Releases: cloudposse/terraform-aws-rds
v1.1.2
🚀 Enhancements
fix: use try on length(var.subnets) @nitrocode (#179)
what
- fix: use try on length(var.subnets)
why
- If the length is used without a try, if subnets are not passed in, the module will fail
- The use case is when the
rdscomponent is deployed withenabled = false, it relies on thevpccomponent which may not be deployed yet. So theenabled: falseflag is used for both thevpcandrds, howeverrdswill still try to retrieve from the remote statevpcwhich will try to pass in a null list of subnets which causes this failure - A local plan against this branch results in the correct plan
references
N/A
🤖 Automatic Updates
Contributors
Assets 2
v1.1.1
fix: Default iops to null (#168) @kbolino (#176)
what
The default value of the iops variable is changed from 0 to null.
why
Resolves an issue with gp3 storage type when allocated storage is below 400 GB. This shouldn't cause problems in other cases, as the parameter is optional at the provider level.
references
🤖 Automatic Updates
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#175)
what
- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.githubrepository - Simplify management of workflows from centralized hub of configuration
Contributors
Assets 2
v1.1.0
Add restore_to_point_in_time variable @joe-niland (#165)
what
- Allow specifying the required configuration to create a database instance via the point-in-time-recovery process
- Update variable description for
snapshot_identifier
why
- Support an alternative creation/DR scenario
references
None
Contributors
Assets 2
v1.0.1
fix: updates README due to failed release @Gowiem (#164)
what
- Updates README to latest
why
- README changes are blocking release #157
references
add feature Master Passwords via Secrets Manager @ByJacob (#157)
what
- add parameter
manage_master_user_password - add parameter
master_user_secret_kms_key_id
why
- allow use new feature
references
🤖 Automatic Updates
chore(deps): update terraform cloudposse/vpc/aws to v2.1.1 @renovate (#162)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/vpc/aws (source) | module | patch | 2.1.0 -> 2.1.1 |
Release Notes
cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)
v2.1.1
Add support for network address usage metrics @lanzrein (#124)
what
This PR adds support for Network Address Usage Metrics on the VPC.
AWS documentation : https://docs.aws.amazon.com/vpc/latest/userguide/network-address-usage.html
Terraform documentation : https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc#enable_network_address_usage_metrics
why
Network Address Usage metrics can help monitor the growth of a VPC and would be useful for any user.
Enable this after creating a VPC does not trigger recreation of the VPC.
references
closes #115
Sync github @max-lobur (#120)
Rebuild github dir from the template
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#125)
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
Contributors
Assets 2
v1.0.0
Support AWS Provider V5 @max-lobur (#159)
what
-
Support AWS Provider V5
- Notable: ID output breaking (in regards to provider version compatibility) change https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-5-upgrade#resourceaws_db_instance
-
Linter fixes
why
Maintenance
references
https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0
Sync github @max-lobur (#156)
Rebuild github dir from the template
Contributors
Assets 2
v0.43.0
- No changes
v0.42.1
🚀 Enhancements
Fix description for engine_version parameter @ragumix (#155)
what
- Fix issue #154 .
Fix description for engine_version parameter. Delete this sentence for engine_version:
Required unless a snapshot_identifier or replicate_source_db is provided.
why
- According to the official documentation (https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/db_instance#engine_version), there is no mentioning that it doesn't need to specify engine_version when you specified snapshot_identifier.
references
Contributors
Assets 2
v0.42.0
v0.41.0
Update AWS provider to 4.49.0 to support gp3 as storage type @nachoy2k (#151)
what
- Update AWS provider to 4.49.0 (latest) to support gp3 as storage type on RDS instances
why
- gp3 storage type is up to 20% cheaper than gp2 and iops or throughput doesn't depend on the volume size.
references
- This is a recent enhancement from AWS for RDS instances: https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-rds-general-purpose-gp3-storage-volumes/
- EBS AWS docs: https://aws.amazon.com/ebs/general-purpose/
Contributors
Assets 2
v0.40.0
feat: add `timeouts` to the instance resource + timeouts variable @DaveSpe (#146)
what
- added timeouts variable (object) to the variables.tf file
- added timeouts code block that references the
var.timeouts.xvariable with default values to theaws_db_instanceresource in main.tf - added variable description in the README.md
why
I ran into an issue where using the module in TF Cloud during creation the run times out.
The instance get's created but due to the run timing out the TF Cloud state does not get updated and each subsequent run would tear down an instance and recreate it, timing out once again.
I added a timeouts variable with default terraform values, which a user can change if they desire in order to accommodate a longer run.
