Triton Provider: firewall_enabled flag is always false

[sodre]

The Triton provider is not picking up the correct state of the firewall in a machine, it always reports it as false.

Steps to reproduce:

• Get an account at Joyent's public cloud and configure it as a provider. You will also need Triton's CLI.
• Create a machine and firewall rule, e.g.

resource "triton_firewall_rule" "bastion-to-vms" {
  rule = "FROM tag role=bastion TO all vms ALLOW tcp PORT 22"
  enabled = true
}

resource "triton_machine" "bastion" {
  name = "bastion"
  package = "t4-standard-512M"
  image = "ffe82a0a-83d2-11e5-b5ac-f3e14f42f12d"
  tags = { 
    role = "bastion"
  } 
  firewall_enabled = true        
  count = 1
}

• Run terraform plan and terraform apply. Everything works fine.
• Run terraform show | grep firewall_enabled. It will show "false"
• Run Joyent's triton inst get bastion | grep firewall_enabled. It will show "true"

If we run terraform plan again, it will create a rule trying to switch the firewall back to enabled, and will recreate the firewall resources.

[sodre]

According to TritonDataCenter/gosdc#23 this is an issue with the vendor API.

[jen20]

Should be fixed by #6119.

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