Releases: cloudposse/terraform-aws-rds
v1.1.3
feat(rds): add database_insights_mode @cdobbyn (#195)
## what- Add
database_insights_mode. - Bump aws provider version requirement to
>= 5.92.0
why
- AWS is asking customers to migrate from the rds performance insights to the cloudwatch performance insights by November 2025. This variable will allow for migrating.
references
chore: add descriptions for example outputs to fix bats tests @RoseSecurity (#199)
## what- Resolve the following:
File: output-descriptions.bats
---------------------------------
private_subnet_cidrs is missing a description
public_subnet_cidrs is missing a description
vpc_cidr is missing a description
---------------------------------
And:
File: input-descriptions.bats
---------------------------------
availability_zones is missing a description
---------------------------------
[!NOTE]
It would be nice if the bats tests didn't run on theexamplesdirectory
🤖 Automatic Updates
Fix go version in tests @osterman (#196)
## what - Update go `1.24`why
- Error loading shared library libresolv.so.2 in Go 1.20
References
Replace Makefile with atmos.yaml @osterman (#193)
## what - Remove `Makefile` - Add `atmos.yaml`why
- Replace
build-harnesswithatmosfor readme genration
References
- DEV-3229 Migrate from build-harness to atmos
Migrate new test account @osterman (#189)
## what - Update `.github/settings.yml` - Update `.github/chatops.yml` fileswhy
- Re-apply
.github/settings.ymlfrom org level to getterratestenvironment - Migrate to new
testaccount
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 (#188)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- Re-apply
.github/settings.ymlfrom org level - Use organization level auto-release settings
references
- DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update .github/settings.yml @osterman (#186)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- Re-apply
.github/settings.ymlfrom org level - Use organization level auto-release settings
references
- DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update .github/settings.yml @osterman (#185)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- Re-apply
.github/settings.ymlfrom org level - Use organization level auto-release settings
references
- DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update release workflow to allow pull-requests: write @osterman (#183)
## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PRwhy
- So we can support commenting on PRs with a link to the release
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
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
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
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
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
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
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/