-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
module:provider can't be a variable #3160
Comments
I think you're saying the same thing as I said in #1819 here... and so I agree. 😀 As far as I know this has never worked since the feature first emerged in a release. It's resulted in my maintaining a separate config for each region rather than a single config with multiple providers, since having reusable modules is more important to me. |
I think this is a duplicate as well: #3072 |
Yep - agreed that this is something we should address. Closing to consolidate around #1819. |
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. |
it seems that the "provider" argument in a module can not be set to a variable. (aws) this makes the combination of modules/multiple providers/aliases not work so well.
my use case is multiple aws accounts, regions.
perhaps this used to not be the case, as this code example shows it being used as such:
#451 (comment)
thanks!
The text was updated successfully, but these errors were encountered: