terraform/internal/terraform/testdata/plan-diffvar/main.tf

resource "aws_instance" "foo" {
  num = "3"
}

resource "aws_instance" "bar" {
  num = aws_instance.foo.num
}
dos2unix 2014-07-28 19:43:00 +02:00			`resource "aws_instance" "foo" {`
core: Ensure context tests comply with plan/apply safety checks Prior to Terraform 0.12 there were certain behaviors we expected from providers that were actually just details of the SDK and not part of the enforced contract. For 0.12 we're now codifying some of these behaviors explicitly via safety checks in core, thus ensuring that all future providers will behave in a consistent way that users can rely on. Unfortunately, due to the hand-written nature of the mock provider implementations we use in tests, they have been getting away with some unusual behaviors that don't match our usual expectations, and our safety checks now detect those as incorrect behaviors. To address this, we make the minimal changes to each test to ensure that its mock provider behaves in a consistent way, which requires that values set in config be represented correctly in the plan and ultimately saved in the new state, without any changes along the way. In particular, the common testDiffFn implementation has historically used a number of special hidden attributes to trigger special behaviors, and our new rules require that these special settings propagate properly through the plan and into the state. 2019-02-12 02:05:24 +01:00			`num = "3"`
dos2unix 2014-07-28 19:43:00 +02:00			`}`

			`resource "aws_instance" "bar" {`
core: Ensure context tests comply with plan/apply safety checks Prior to Terraform 0.12 there were certain behaviors we expected from providers that were actually just details of the SDK and not part of the enforced contract. For 0.12 we're now codifying some of these behaviors explicitly via safety checks in core, thus ensuring that all future providers will behave in a consistent way that users can rely on. Unfortunately, due to the hand-written nature of the mock provider implementations we use in tests, they have been getting away with some unusual behaviors that don't match our usual expectations, and our safety checks now detect those as incorrect behaviors. To address this, we make the minimal changes to each test to ensure that its mock provider behaves in a consistent way, which requires that values set in config be represented correctly in the plan and ultimately saved in the new state, without any changes along the way. In particular, the common testDiffFn implementation has historically used a number of special hidden attributes to trigger special behaviors, and our new rules require that these special settings propagate properly through the plan and into the state. 2019-02-12 02:05:24 +01:00			`num = aws_instance.foo.num`
dos2unix 2014-07-28 19:43:00 +02:00			`}`