Mitchell Hashimoto c6d0333dc0 flatmap: mark computed list as a computed value in Expand ... Fixes #12183 The fix is in flatmap for this but the entire issue is a bit more complex. Given a schema with a computed set, if you reference it like this: lookup(attr[0], "field") And "attr" contains a computed set within it, it would panic even though "field" is available. There were a couple avenues I could've taken to fix this: 1.) Any complex value containing any unknown value at any point is entirely unknown. 2.) Only the specific part of the complex value is unknown. I took route 2 so that the above works without any computed (since "name" is not computed but something else is). This may actually have an effect on other parts of Terraform configs, however those similar configs would've simply crashed previously so it shouldn't break any pre-existing configs.		2017-02-23 10:03:59 -08:00
..
expand_test.go	flatmap: mark computed list as a computed value in Expand	2017-02-23 10:03:59 -08:00
expand.go	flatmap: mark computed list as a computed value in Expand	2017-02-23 10:03:59 -08:00
flatten_test.go	flatmap: add richer API to resulting flattened map	2014-07-09 15:26:47 -07:00
flatten.go	flatmap: add richer API to resulting flattened map	2014-07-09 15:26:47 -07:00
map_test.go	flatmap: add Contains	2014-07-14 21:40:29 -07:00
map.go	fmt	2014-07-14 21:56:34 -07:00