Releases: cloudposse/terraform-aws-acm-request-certificate
v0.13.1
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#43)
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
v0.13.0
v0.12.0
remove uneeded tolist as is set now @pjaudiomv (#38)
what
there is no need to convert to a list anymore as its a set
why
fixes bug introduced by me :)
references
- issue from slack thread https://sweetops.slack.com/archives/CB6GHNLG0/p1609784495001600
v0.11.0
updates for tf 0.14 and aws provder 3.x @pjaudiomv (#35)
what
- Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard
why
- Support Terraform 0.14
- Support AWS Provider >= 3.x
references
- https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-3-upgrade#domain_validation_options-changed-from-list-to-set
- closes #26 #27
Previously, the domain_validation_options attribute was a list type and completely unknown until after an initial terraform apply. This generally required complicated configuration workarounds to properly create DNS validation records since referencing this attribute directly could produce errors similar to the below:
Error: Invalid for_each argument
on main.tf line 16, in resource "aws_route53_record" "existing":
16: for_each = aws_acm_certificate.existing.domain_validation_options
The "for_each" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the for_each depends on.
The domain_validation_options attribute is now a set type and the resource will attempt to populate the information necessary during the planning phase to handle the above situation in most environments without workarounds. This change also prevents Terraform from showing unexpected differences if the API returns the results in varying order.
v0.10.0
0.9.0 Fix dns validation processing
what
- Fix dns validation processing
why
- Allow the DNS processing to work with wildcard certificates
0.8.0: Fix aws provider version for latest terraform 0.13 (#29)
what
- Updated the required provider versions to get this module working with the latest terraform 0.13 release
why
- Without this patch this module does not work with terraform 0.13.4
0.7.0: Remove appending of a dot to the zone name (#22)
What
- Fixes a bug with an extra dot when using
var.zone_name>var.domain_name
Why
- The appending of the dot breaks the search of the zone when referencing the name from an existing aws_route53_zone resource because the name property already contains the dot.
0.6.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#28)
## 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.5.0: Updates to ChatOps - Automated commit (#23)
## 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