You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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.		9 years ago
..
data_source.go	provider/test: Add test of data source count.index	10 years ago
data_source_test.go	providers/test: additional testing via integration tests	9 years ago
provider.go	flatmap: mark computed list as a computed value in Expand	9 years ago
provider_test.go	core: Fix issues with ignore_changes	10 years ago
resource.go	provider/test: Add test of data source count.index	10 years ago
resource_gh12183.go	flatmap: mark computed list as a computed value in Expand	9 years ago
resource_gh12183_test.go	flatmap: mark computed list as a computed value in Expand	9 years ago
resource_test.go	Add a provider test for a list of maps	9 years ago