Closed KalenWessel closed 1 year ago
I don't see the issue immediately. Could you try simplifying it by removing for_each
from both?
If it still doesn't work, try running example 2
as-is - https://github.com/terraform-aws-modules/terraform-aws-acm/blob/27e32f53cd6cbe84287185a37124b24bd7664e03/examples/complete-dns-validation/main.tf#L54-L101
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
I'm attempting to follow the example using multiple providers to create certificates in one account and DNS validation in another account.
Versions
Module version [Required]: terraform-aws-modules/acm/aws 4.3.2
Terraform version: Terraform v1.5.1
Provider version(s): registry.terraform.io/hashicorp/aws v5.5.0
Reproduction Code [Required]
Steps to reproduce the behavior:
terraform init
terraform plan
Expected behavior
I would expect to see ACM certs in the default AWS provider account and Route53 txt records for validation in my AWS parent dns account.
Actual behavior