terraform/configs/configupgrade/testdata/valid/element-of-set/input/element-of-set.tf

resource "test_instance" "a" {
  subnet_ids = ["boop"] # this attribute takes a set of strings
}

output "b" {
  value = "${element(test_instance.a.subnet_ids, 0)}"
}
configs/configupgrade: Detect and fix element(...) usage with sets Although sets do not have indexed elements, in Terraform 0.11 and earlier element(...) would work with sets because we'd automatically convert them to lists on entry to HIL -- with an arbitrary-but-consistent ordering -- and this return an arbitrary-but-consistent element from the list. The element(...) function in Terraform 0.12 does not allow this because it is not safe in general, but there was an existing pattern relying on this in Terraform 0.11 configs which this upgrade rule is intended to preserve: resource "example" "example" { count = "${length(any_set_attribute)}" foo = "${element(any_set_attribute, count.index}" } The above works because the exact indices assigned in the conversion are irrelevant: we're just asking Terraform to create one resource for each distinct element in the set. This upgrade rule therefore inserts an explicit conversion to list if it is able to successfully provide that the given expression will return a set type: foo = "${element(tolist(any_set_attribute), count.index}" This makes the conversion explicit, allowing users to decide if it is safe and rework the configuration if not. Since our static type analysis functionality focuses mainly on resource type attributes, in practice this rule will only apply when the given expression is a statically-checkable resource reference. Since sets are an SDK-only concept in Terraform 0.11 and earlier anyway, in practice that works out just right: it's not possible for sets to appear anywhere else in older versions anyway. 2019-02-21 01:28:15 +01:00			`resource "test_instance" "a" {`
			`subnet_ids = ["boop"] # this attribute takes a set of strings`
			`}`

			`output "b" {`
			`value = "${element(test_instance.a.subnet_ids, 0)}"`
			`}`