Closed dannyibishev closed 2 years ago
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
Any chance this can be looked at
Would be great to see this one merged! How does it handle the case of using single account? Does the user still need to path 2 providers even if it's the same one?
@antonbabenko any chance this can be merged?
This issue has been resolved in version 4.1.0 :tada:
Thanks for the feature! Already updated our code - works like a charm. No need to create validation records manually anymore.
Thank you for the confirmation, @mputilin !
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.
Description
The proposed changes will allow both cross-account and single account ACM creation with DNS validation.
Motivation and Context
I needed to create my ACM certificates in account B but my hosted zone belongs to Account A. These changes allowed me to meet this requirement.
Breaking Changes
I believe the two providers will now always be required and need to be explicitly passed down.
In the module call, people will now need to pass the providers block with the two required providers.
or if they use a single account then the following block should still work
How Has This Been Tested?
I have tested by calling the fork with my branch
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request