_This issue was originally opened by @fabian-dev as hashicorp/terraform#12111. It was migrated here as part of the provider split. The original body of the issue is below._
By now using the aws_acm_certificate
data source is no option for us. This is because we want to renew our ACM certs on a regular basis.
During our renewal phase and after issuing new certs, there will be more than one cert present (with equal domain names).
TF will then fail with:
data.aws_acm_certificate.xxx: Multiple certificates for domain "xxx" found in this region.
If I could use a most_recent=true flag (like it is with the aws_ami
data source), I could gracefully apply the TF configuration during the renewal phase and switch to new certs.
I would appreciate your thought on this.
Cheers Fabian
Thanks for your patience here, everyone! The most_recent
functionality is now in master and will release in v1.9.0 of the AWS provider. Happy Terraform'ing! 🎉
This has been released in terraform-provider-aws version 1.9.0. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.
I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!
Most helpful comment
Thanks for your patience here, everyone! The
most_recent
functionality is now in master and will release in v1.9.0 of the AWS provider. Happy Terraform'ing! 🎉