You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the addition of for_each capability for modules in terraform 0.13 we finally got the missing feature we all wanted but it is still incomplete in case we need to instantiate modules for different providers. This is true especially in the case when calling the same module is needed but for different account/region - and unfortunately many AWS features still need to be managed on per account/ per region level
Unfortunately this is not something that can be added to the 0.13 release, since it would involve some major internal changes to Terraform to accomplish. We have some open issues requesting the ability to dynamically assign providers already #25244 and #19932. We can track the individual features there.
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.
ghost
locked as resolved and limited conversation to collaborators
Oct 11, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Terraform Version
Terraform v0.13.0
Use-cases
With the addition of for_each capability for modules in terraform 0.13 we finally got the missing feature we all wanted but it is still incomplete in case we need to instantiate modules for different providers. This is true especially in the case when calling the same module is needed but for different account/region - and unfortunately many AWS features still need to be managed on per account/ per region level
Proposal
Have the following structure possible:
The text was updated successfully, but these errors were encountered: