[UX2.0] sdwan_transport_management_vpn_profile_parcel fails when ipv6 route next hop does not specify administrative_distance

[tzarski0]

If you configure sdwan_transport_management_vpn_profile_parcel with ipv6 route without explicitly specifying admin distance:

resource "sdwan_transport_management_vpn_profile_parcel" "example" {
  name                       = "Example"
  description                = "My Example"
  feature_profile_id         = "f6dd22c8-0b4f-496c-9a0b-6813d1f8b8ac"
  ipv6_static_routes = [
    {
      prefix = "2002::/16"
      next_hops = [
        {
          address                 = "2001:0:0:1::1"
        }
      ]
    }
  ]
}

it fails with:

│ Failed to configure object (PUT), got error: HTTP Request failed: StatusCode 400,
│ {"error":{"message":"Invalid Json Payload
│ Input","code":"SCHVALID0001","details":"{\"Validation Errors\":{\"Required But Missing
│ Attributes\":[\"data.ipv6Route[0].oneOfIpRoute.nat\",\"data.ipv6Route[0].oneOfIpRoute.nextHopContainer.nextHop[0].distance\",\"data.ipv6Route[0].oneOfIpRoute.null0\"],\"Not
│ Defined In Schema
│ Attributes\":[\"data.ipv6Route[2].oneOfIpRoute.nextHopContainer\"]}}","type":"error"}}
╵

[tzarski0]

@seconroy even after the fix, I'm still getting:

│ Failed to configure object (PUT), got error: HTTP Request failed: StatusCode 400,
│ {"error":{"message":"Invalid Json Payload Input","code":"SCHVALID0001","details":"{\"Validation
│ Errors\":{\"Required But Missing Attributes\":[\"data.ipv6Route[0].oneOfIpRoute\"]}}","type":"error"}}

[tzarski0]

Resolved in release 0.5.1