Closed vincenthanjs closed 5 months ago
Hi,
The provider supports VCF 4.5.X as of now. This bug will have to wait until 5.1.X support.
Best Regards
Hi @dimitarproynov,
Actually the VCF 4.5.x API already have the "vmManagementPortgroupName" and "vmManagementPortgroupVlan". Can we make it work for current provider?
@vincenthanjs this property was actually added in 5.1.0 It is listed as "introduced" here https://developer.vmware.com/apis/vcf/5.1.0/data-structures/NsxTEdgeNodeSpec
I think the confusion comes from the fact that the docs site lists all optional properties when you expand the example payload even if they are not part of the selected version.
We will tackle this one once we move on to VCF 5
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.
Code of Conduct
Description
In the VCF API 4.5 onwards, there is option to add vmManagementPortgroupName and vmManagementPortgroupVlan but however its not an option in the terraform provider. Could you please add those in? https://developer.vmware.com/apis/vcf/latest/v1/edge-clusters/post/
Use Case(s)
Specify a dedicated management portgroup and vlan for NSX-T Edges in VI Workload Domain.
Potential Configuration
"vmManagementPortgroupName": "string", "vmManagementPortgroupVlan": 0
References
https://developer.vmware.com/apis/vcf/latest/v1/edge-clusters/post/