-
-
Notifications
You must be signed in to change notification settings - Fork 92
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 does not support for_each due to hard coded providers #48
Labels
bug
🐛 An issue with the system
Comments
Closed
Hi all, any update in this feature? |
I think this would be a good extension to this module. Since this would be a breaking change, we'd require a migration doc, updated examples, and move to the next major version of 1.x. We would also try to close as many open issues as possible with prs for that release. I'd like to work on this when I find the time. Feel free to contribute the change too and we will review. |
nitrocode
changed the title
Module does not support for_each
Module does not support for_each due to hard coded providers
Jun 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
The module is unable to support
for_each
since it contains provider configuration:Expected Behavior
The module should support
for_each
loops.Additional Context
I believe passing the providers into the module (instead of configuring the providers w/in the module) would do the trick. I labeled this as bug but it may be a feature request instead.
The text was updated successfully, but these errors were encountered: