terraform woefully mishandles network pools.

[bahamat]

Terraform Version

0.10.4, provider version 0.1.3

Affected Resource(s)

• triton_network
• triton _machine

Terraform Configuration Files

provider "triton" {
    url = "https://us-sw-1.api.joyent.com/"
}

data "triton_image" "image" {
    name = "base-64-lts"
    version = "16.4.1"
}

data "triton_network" "public" {
    name = "Joyent-SDC-Public"
}

resource "triton_machine" "test" {
    package = "g4-highcpu-128M"
    image   = "${data.triton_image.image.id}"
    nic {
        network = "${data.triton_network.public.id}"
    }
}

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Expected Behavior

The instances should not be unnecessarily modified

Actual Behavior

Every time terraform apply is run it deletes the nic and adds a new nic. This has the side effect of rebooting the instance, and making terraform unusable.

Steps to Reproduce

1. terraform apply
2. terraform apply

[bahamat]

Duplicate of #30.