dependency resolution broken

[MerlinDMC]

Given the following config:

resource "null_resource" "foo" {
  count = 2
  provisioner "local-exec" {
    command = "echo ${null_resource.foo.1.id}"
  }
}

Expected order of creation would be:

• null_resource.foo.1
• null_resource.foo.0

Current computed order is:

• null_resource.foo.0
• null_resource.foo.1

(it creates both resources in parallel)

which makes it fail during the provisioning step:

null_resource.foo.0: Creating...
null_resource.foo.1: Creating...
null_resource.foo.0: Error: 1 error(s) occurred:

* Resource 'null_resource.foo.1' not found for variable 'null_resource.foo.1.id'
null_resource.foo.1: Provisioning with 'local-exec'...
null_resource.foo.1 (local-exec): Executing: /bin/sh -c "echo 3030871191733529834"
null_resource.foo.1 (local-exec): 3030871191733529834
null_resource.foo.1: Creation complete
Error applying plan:

1 error(s) occurred:

* 1 error(s) occurred:

* 1 error(s) occurred:

* Resource 'null_resource.foo.1' not found for variable 'null_resource.foo.1.id'

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

[mitchellh]

This is indeed a problem. Thanks. Tagged.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.