Releases: cloudposse/terraform-aws-documentdb-cluster
Releases · cloudposse/terraform-aws-documentdb-cluster
v0.10.1
Update module versions. Update terratest @aknysh (#26)
what
- Update module versions
- Update
terratest
why
- Keep up to date
- Add random attributes when provisioning with
terratest
🤖 Automatic Updates
Update Terraform cloudposse/route53-cluster-hostname/aws to v0.10.0 @renovate (#22)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/route53-cluster-hostname/aws (source) | terraform | minor | 0.8.0 -> 0.10.0 |
Release Notes
cloudposse/terraform-aws-route53-cluster-hostname
v0.10.0
Terraform 0.14 upgrade @maximmi (#32)
#### what - Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard #### why - Support Terraform 0.14v0.9.0
Update `context.tf` and github actions @htplbc (#31)
##### what * Update to `context.tf` ##### why * Keep the module up to datev0.10.0
Pass dns_name to terraform-aws-route53-cluster-hostname instead of name @michael-careplanner (#24)
what
- Fixes incorrect DNS records when setting custom records in R53 by passing
dns_namerather thannametoterraform-aws-route53-cluster-hostname
why
terraform-aws-route53-cluster-hostnamechanged how to pass the DNS name in between 0.5.0 and 0.7.0+- In 0.5.0 the DNS record was created used
var.name(https://github.com/cloudposse/terraform-aws-route53-cluster-hostname/blob/0.5.0/main.tf#L4) - which is what this module passes. - Since 0.7.0 the DNS record created uses
var.dns_nameif set, defaulting tomodule.this.idif not (https://github.com/cloudposse/terraform-aws-route53-cluster-hostname/blob/0.7.0/main.tf#L3) - This results in the custom DNS names passed in this module not generating the correct R53 records.
v0.9.0
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#25)
what
- update context.tf to v0.23.0
- minimum required Terraform version bumped to 0.13.0
- readme updated, Bridgecrew compliance badges added
why
- It allows for setting the letter case of tag names and labels
- we have dropped support for Terraform 0.12
- To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant
v0.8.0
0.7.0: Also support aws provider 3+ (#17)
## what Set to use the latest version of dependencies and set to accept higher aws provider versions (3+) ## why the latest aws provider now is 3.14.1, for this module to stay relevant it need to start support 3+. There might be a point in creating 2 separate branches/tracks in the future since some 3+ things are not compatible with some 2+ things and vice versa.. I do not now if this module includes any issues like that, but the included "complete" test is ok with using the latest 3.14.1 provider at least. ## references Direct links to the updated modules if curious what has changed in the versions (I didnt analyze just ran test and it worked https://github.com/cloudposse/terraform-aws-vpc https://github.com/cloudposse/terraform-aws-dynamic-subnets https://github.com/cloudposse/terraform-aws-route53-cluster-hostname Not for these particular changes Im doing a PR for now, but for reference what has changed between 2 and 3. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-3-upgrade
0.6.0: add new attributes: auto_minor_version_upgrade, preferred_maintenance_window
add new attributes: auto_minor_version_upgrade, preferred_maintenance…
0.5.2
0.5.1
0.5.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#11)
## What 1. Update Version Pinning for Terraform to support 0.13 ## Why 1. This is a relatively minor update that the CloudPosse module already likely supports. 1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.
0.4.0: Updates to ChatOps - Automated commit (#10)
## What * Adds chatops commands - '/test all' - '/test bats' - '/test readme' - '/test terratest' * Drops codefresh * Drops slash-command-dispatch * Removes codefresh badge * Rebuilds README ## Why * Change over from codefresh to GH Actions * Facilitate testing of PRs from forks