-
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
Indexing of computed lists does not work #8695
Comments
mitchellh
added a commit
that referenced
this issue
Dec 11, 2016
Fixes #8695 When a list count was computed in a multi-resource access (foo.bar.*.list), we were returning the value as empty string. I don't actually know the histocal reasoning for this but this can't be correct: we must return unknown. When changing this to unknown, the new tests passed and none of the old tests failed. This leads me further to believe that the return empty string is probably a holdover from long ago to just avoid crashes or UUIDs in the plan output and not actually the correct behavior.
Have a fix queued in the referenced PR! |
Awesome! |
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 and limited conversation to collaborators
Apr 18, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform v0.7.3
Affected Resource(s)
n/a
-- interpolation issue.Terraform Configuration Files
Debug Output
https://gist.github.com/jszwedko/db8a5b43a61e7139fef6a195e1c588cb
Expected Behavior
A route53 record is created using the private IPs from the created network interfaces.
Actual Behavior
Steps to Reproduce
terraform plan
Important Factoids
If you comment out the
aws_route53_record
,terraform plan
andterraform apply
you can than uncomment it and it creates correctly (now that the value it is indexing is no longer computed).References
#7906 is a related issue
The text was updated successfully, but these errors were encountered: