opentofu/internal/tofu/testdata/apply-multi-var-order/main.tf

variable "num" {
  default = 15
}

resource "aws_instance" "bar" {
  count = "${var.num}"
  foo   = "index-${count.index}"
}

output "should-be-11" {
  value = "${element(aws_instance.bar.*.foo, 11)}"
}
update test fixtures Update test fixtures to work in our new world. This is mostly changing out attribute names for those in the schema, adding Providers to states, and updating the test-fixture configurations. 2018-05-23 12:39:36 -05:00			`variable "num" {`
core: fix test fixtures for HCL2 syntax idiom A number of our test fixtures were previously using the non-idiomatic form of including a single child attribute all on one line with the block header and bounding braces. This non-idiomatic form is an error in HCL2, and hclfmt has always "fixed" it to the expected form of each attribute being on a line of its own, and so here we just update all the affected test fixtures to canonical form (using hclfmt), allowing them to be parsed as intended. Since the these entire files were processed with hclfmt, there are some other unrelated style changes included in situations where the file layouts were non-idiomatic in other ways. 2018-05-04 22:26:07 -05:00			`default = 15`
			`}`
terraform: multi-var ordering is by count Fixes #9444 This appears to be a regression from 0.7.0, but there were no tests covering it so we missed it and changed the behavior at some point! Oh no. This PR make the ordering of multi-var access: `resource.name.*.attr` consistent: it is the ordering of the count, not the lexical ordering of the value. This allows behavior where two lists are indexed by count index and can be assumed to be related (for example user data for an aws instance, as shown in the above referenced issue). Two new context tests added to cover this case. 2016-11-04 13:07:01 -05:00
			`resource "aws_instance" "bar" {`
update test fixtures Update test fixtures to work in our new world. This is mostly changing out attribute names for those in the schema, adding Providers to states, and updating the test-fixture configurations. 2018-05-23 12:39:36 -05:00			`count = "${var.num}"`
core: fix test fixtures for HCL2 syntax idiom A number of our test fixtures were previously using the non-idiomatic form of including a single child attribute all on one line with the block header and bounding braces. This non-idiomatic form is an error in HCL2, and hclfmt has always "fixed" it to the expected form of each attribute being on a line of its own, and so here we just update all the affected test fixtures to canonical form (using hclfmt), allowing them to be parsed as intended. Since the these entire files were processed with hclfmt, there are some other unrelated style changes included in situations where the file layouts were non-idiomatic in other ways. 2018-05-04 22:26:07 -05:00			`foo = "index-${count.index}"`
terraform: multi-var ordering is by count Fixes #9444 This appears to be a regression from 0.7.0, but there were no tests covering it so we missed it and changed the behavior at some point! Oh no. This PR make the ordering of multi-var access: `resource.name.*.attr` consistent: it is the ordering of the count, not the lexical ordering of the value. This allows behavior where two lists are indexed by count index and can be assumed to be related (for example user data for an aws instance, as shown in the above referenced issue). Two new context tests added to cover this case. 2016-11-04 13:07:01 -05:00			`}`

			`output "should-be-11" {`
core: fix test fixtures for HCL2 syntax idiom A number of our test fixtures were previously using the non-idiomatic form of including a single child attribute all on one line with the block header and bounding braces. This non-idiomatic form is an error in HCL2, and hclfmt has always "fixed" it to the expected form of each attribute being on a line of its own, and so here we just update all the affected test fixtures to canonical form (using hclfmt), allowing them to be parsed as intended. Since the these entire files were processed with hclfmt, there are some other unrelated style changes included in situations where the file layouts were non-idiomatic in other ways. 2018-05-04 22:26:07 -05:00			`value = "${element(aws_instance.bar.*.foo, 11)}"`
terraform: multi-var ordering is by count Fixes #9444 This appears to be a regression from 0.7.0, but there were no tests covering it so we missed it and changed the behavior at some point! Oh no. This PR make the ordering of multi-var access: `resource.name.*.attr` consistent: it is the ordering of the count, not the lexical ordering of the value. This allows behavior where two lists are indexed by count index and can be assumed to be related (for example user data for an aws instance, as shown in the above referenced issue). Two new context tests added to cover this case. 2016-11-04 13:07:01 -05:00			`}`