Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Cross-account DNS and ACM resource creation #114

Merged
merged 7 commits into from
Aug 26, 2022

Conversation

antonbabenko
Copy link
Member

@antonbabenko antonbabenko commented Aug 26, 2022

Follow up for #108

Fixes #108

PS: I had no push access to the original fork, so I have created this PR instead.

dannyibishev and others added 5 commits May 10, 2022 14:03
add changes made from the pre-commit and the recommended PR guidelines
the coniguration_aliases is enough to make this work without the default provider blocks
@antonbabenko antonbabenko changed the title feat crossaccount feat: Cross-account DNS and ACM resource creation Aug 26, 2022
@antonbabenko
Copy link
Member Author

@dannyibishev Thank you for the initial PR.

@antonbabenko antonbabenko merged commit e24bb59 into master Aug 26, 2022
@antonbabenko antonbabenko deleted the feat-crossaccount branch August 26, 2022 14:25
antonbabenko pushed a commit that referenced this pull request Aug 26, 2022
## [4.1.0](v4.0.1...v4.1.0) (2022-08-26)

### Features

* Cross-account DNS and ACM resource creation ([#114](#114)) ([e24bb59](e24bb59))
@antonbabenko
Copy link
Member Author

This PR is included in version 4.1.0 🎉

@OneBadSanta
Copy link

I am having difficulty getting an example included in this PR to work

https://github.com/terraform-aws-modules/terraform-aws-acm/blob/master/examples/complete-dns-validation/main.tf#L31-L52

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

@antonbabenko
Copy link
Member Author

@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).

@OneBadSanta
Copy link

@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?

https://github.com/terraform-aws-modules/terraform-aws-acm/blob/master/examples/complete-dns-validation/main.tf#L13-L52

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

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants