Closed antonbabenko closed 2 years ago
@dannyibishev Thank you for the initial PR.
This PR is included in version 4.1.0 :tada:
I am having difficulty getting an example included in this PR to work
When looking at main.tf, i do not see these providers located in resource sections. Am I missing something? How do I use this for cross-account?
Thanks
@OneBadSanta providers
blocks with different aliases (acm and route53) can be declared as shown in README here - https://github.com/terraform-aws-modules/terraform-aws-acm#usage-with-route53-dns-validation-and-separate-aws-providers . In the example you point, both instance of AWS provider are the same (aws
).
@antonbabenko Thanks for the response. Right. I understand what you're saying. In that the module needs to be split apart in order to use 2 different providers. For me personally, this seems to miss the point of the usefulness of having a module for this purpose. I guess the question how is it possible that example one even works?
The resources do not in v4.1.0 do not have multiple providers. There is no mention of aws.acm and aws.dns, only the global default aws.
providers = {
aws.acm = aws,
aws.dns = aws
}
Am I missing something? Does my questions make sense?
Thanks
I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Follow up for #108
Fixes #108
PS: I had no push access to the original fork, so I have created this PR instead.