[Bug]: Unknown changes to metal_ports when adding VLAN

[nebb00]

Terraform Version

1.12.1

Equinix Provider Version

3.9.0

Effected Terraform Resources

equinix_metal_port
equinix_vlan

Issue

When I add a create a new VLAN and assign to a metal port during the same terraform apply. It will not correctly output the changes to the port.

  # module.metal[0].equinix_metal_port.nic["sg5-gms-res-11e.as.equinixms.com.eth3"] will be updated in-place
  ~ resource "equinix_metal_port" "nic" {
        id                = "6894fe0f-665f-40e9-adf9-0716e2d8a938"
        name              = "eth3"
      ~ vlan_ids          = [
          - "295fba02-3a5f-4ce9-a670-223c5d6da5d4",
          - "7a67ca82-6cfa-4e34-b0cb-2e50f3515edb",
          - "9139fde9-e95f-4dfb-9046-4a6fcee8c5dc",
          - "d65461f4-3786-4236-97cf-2c20516ad263",
          - "f09a1305-4592-47fd-9570-0e840edb562a",
          - "f5f62905-7054-4302-b132-16a2650acb6d",
          - "f6ad545a-1405-40c9-984f-4cb888456d3d",
        ] -> (known after apply)
        # (10 unchanged attributes hidden)
    }

but if you create the VLAN first, then assign to the metal_port. It shows correctly.

  # module.metal[0].equinix_metal_port.nic["sg5-gms-res-11e.as.equinixms.com.eth3"] will be updated in-place
  ~ resource "equinix_metal_port" "nic" {
        id                = "6894fe0f-665f-40e9-adf9-0716e2d8a938"
        name              = "eth3"
      ~ vlan_ids          = [
          + "4556d67e-8f90-4ec2-afc7-aae5b3319c03",
            # (9 unchanged elements hidden)
        ]
        # (10 unchanged attributes hidden)
    }

Steps to Reproduce

Create VLAN and assign to a Metal port during the same execution

[displague]

Is the problem described about a maximum number of VLAN attachments being applied or returned in a single execution? Eventual consistency through drift and updates is a hallmark of Terraform, but I would expect to find all of the VLAN responses returned in the API port response received after the changes have been made. This may be an API response timing issue rather than something Terraform can/should await without a behavioral flag (arguable).

[nebb00]

Is the problem described about a maximum number of VLAN attachments being applied or returned in a single execution? Eventual consistency through drift and updates is a hallmark of Terraform, but I would expect to find all of the VLAN responses returned in the API port response received after the changes have been made. This may be an API response timing issue rather than something Terraform can/should await without a behavioral flag (arguable).

Its not about the quantity or maximums, nor drift. Its when you create a vlan and apply to an existing port in the same execution, terraform does not show the correct state. The example at the top, shows the example when i create a single new vlan, seperately or together.