Is your feature request related to a problem? Please describe.
Currently it's not possible to create a network connection with dualstack ip adress pools. There are no options for that. You can create a vm with an ip adress pool but you can't choose if it's ipv4 or ipv6 like in the GUI. It's some kind of random behaviour.
Describe the solution you'd like
In the XML Representation of NetworkConnection there are SecondaryIpAddress and SecondaryIpAddressAllocationMode elements defined. This could be added to the current types for api version 34.0.
Is your feature request related to a problem? Please describe.
Currently it's not possible to create a network connection with dualstack ip adress pools. There are no options for that. You can create a vm with an ip adress pool but you can't choose if it's ipv4 or ipv6 like in the GUI. It's some kind of random behaviour.
Describe the solution you'd like
In the XML Representation of NetworkConnection there are SecondaryIpAddress and SecondaryIpAddressAllocationMode elements defined. This could be added to the current types for api version 34.0.
Describe alternatives you've considered
I have also tried to add this here, but I am struggeling a bit. I have added the secondary elements in NetworkConnection type (https://github.com/vmware/go-vcloud-director/commit/31bf4542a02862455cae4abba71b7a9759b93e6c)
I applied my config with an customized terraform vcd provider here.
When I deploy a vm with secondary elements I get the following error.
Additional context
No response