vcd_nsxt_network_imported activating dual stack after the fact recreates the segment

[bogi0704]

Hello,

if the resource has already existed with an IPv4 address, adding a secondary IPv6 address and setting the segment to dual stack will lead to recreation. The VCD UI allows the user to change an IPv4 only subnet to Dual Stack.

Terraform Version

Terraform v1.8.5
on linux_amd64
provider registry.terraform.io/vmware/vcd v3.14.1

Affected Resource(s)

• vcd_nsxt_network_imported

Terraform Configuration Files

-/+ resource "vcd_nsxt_network_imported" "main" {
      + dual_stack_enabled       = true
      + dvpg_id                  = (known after apply)
      ~ id                       = "urn:vcloud:network:5de0c4ec-4325-4847-8d22-874457cb4c8c" -> (known after apply)
        name                     = "segmentName"
      ~ nsxt_logical_switch_id   = "9ec6781a-0eb3-4c5c-8cc4-1ca2cf60750b" -> (known after apply)
      + secondary_gateway        = "fd8a:3e2b:ce5::1" # forces replacement
      + secondary_prefix_length  = "48" # forces replacement
      ~ vdc                      = "vdcname" -> (known after apply)
        # (8 unchanged attributes hidden)

      + secondary_static_ip_pool {
          + end_address   = "fd8a:3e2b:ce5:ffff:ffff:ffff:ffff:fffe"
          + start_address = "fd8a:3e2b:ce5::2"
        }

        # (1 unchanged block hidden)
    }

Expected Behavior

The network should just be changed rather than being recreated.

Actual Behavior

The network is up for recreation

Steps to Reproduce

1. create an IPv4-only network first
2. add a secondary IPv6 gateway
3. terraform plan