"diffs didn't match during apply" with google_compute_firewall

[julienvey]

Tested with 0.3.7 and last version from master

The following tf file causes the diffs didn't match during apply error when running terraform apply

resource "google_compute_network" "subnet_1" {
    name = "subnet-test"
    ipv4_range = "10.0.0.0/24"
}

resource "google_compute_firewall" "test" {
  name = "test-1080"
  network = "${google_compute_network.subnet_1.name}"
  source_ranges = ["${google_compute_address.test_addr.address}/32"]
  allow {
    protocol = "tcp"
  }
}

resource "google_compute_address" "test_addr" {
    name = "test-addr"
}

The full log of the command http://pastebin.com/RgncfeZU

Running terraform apply a second time works well http://pastebin.com/16PdNUFL

However, if I remove the dependency between google_compute_firewall and google_compute_address, there is no error

resource "google_compute_network" "subnet_1" {
    name = "subnet-test"
    ipv4_range = "10.0.0.0/24"
}

resource "google_compute_firewall" "test" {
  name = "test-1080"
  network = "${google_compute_network.subnet_1.name}"
  source_ranges = ["1.1.1.1/32"]
  allow {
    protocol = "tcp"
  }
}

The log of the command http://pastebin.com/4PEuWdKq

[erjohnso]

/cc @sparkprime

[sparkprime]

First impression is this looks very similar to #634

[sparkprime]

@mitchellh thoughts?

[sparkprime]

There is also no error if you remove the dependency on the network (by using the "default" network instead)

[mitchellh]

I haven't had a chance to look at this yet but its certainly a core issue. Tagged accordingly and we'll make sure to take a look very soon.

[mitchellh]

Reproduced.

Personal notes so far: The diff isn't properly detecting the set as computed. It is showing up like this (important line): source_ranges.1902308426: "" => "74D93920-ED26-11E3-AC10-0800200C9A66/32". This should show up as source_ranges.1902308426: "" => "<computed>" or something CLOSE to that.

[mitchellh]

Fixed by #1082 once merged.

[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.