-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Maps not coerced to objects for input variables #24092
Comments
Hi @davecardwell, Thanks, it appears the conversion functions aren't handling this case correctly. The good news is that if you're only dealing with literals or expressions, they will initially be typed as an object and pass through. The |
Thanks for the speedy response, @jbardin. I used the I can set the variable type as I went digging and raised the issue with |
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. |
Terraform Version
Terraform Configuration Files
main.tf
child/child.tf
Debug Output
https://gist.github.com/davecardwell/94c238e4f12d7d5612668a3747a35ea1
Expected Behavior
From Conversion of Complex Types in the docs I expected the
map
to be converted to anobject
and accepted as a valid value.Actual Behavior
Steps to Reproduce
terraform init
terraform validate
The text was updated successfully, but these errors were encountered: