api: change CoresPerNumaNode to a pointer type

This is needed for the use case of setting CoresPerNumaNode to '0'.
luisdavim · Jul 2, 2024 · 29b1bce · 29b1bce
1 parent 147b39c
commit 29b1bce
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/gen/vim_wsdl.rb b/gen/vim_wsdl.rb
@@ -262,7 +262,7 @@ def any_type?
 
   def pointer_type?
     ["UnitNumber"].include?(var_name) or
-      optional? && ["IpPoolId", "OwnerId", "GroupId", "MaxWaitSeconds", "Reservation", "Limit", "OverheadLimit", "ResourceReductionToToleratePercent"].include?(var_name)
+      optional? && ["CoresPerNumaNode", "IpPoolId", "OwnerId", "GroupId", "MaxWaitSeconds", "Reservation", "Limit", "OverheadLimit", "ResourceReductionToToleratePercent"].include?(var_name)
   end
 
   def var_type

diff --git a/vim25/types/types.go b/vim25/types/types.go
@@ -91361,7 +91361,7 @@ type VirtualMachineVirtualNuma struct {
 	// vNUMA node.
 	// If set to be non zero, VM uses the value as vNUMA node size.
 	// If unset, the VM continue to follow the behavior in last poweron.
-	CoresPerNumaNode int32 `xml:"coresPerNumaNode,omitempty" json:"coresPerNumaNode,omitempty"`
+	CoresPerNumaNode *int32 `xml:"coresPerNumaNode" json:"coresPerNumaNode,omitempty"`
 	// Capability to expose virtual NUMA when CPU hotadd is enabled.
 	//
 	// If set to true, ESXi will consider exposing virtual NUMA to
@@ -91389,7 +91389,7 @@ type VirtualMachineVirtualNumaInfo struct {
 	// field should be ignored.
 	// In other cases, this field represents the virtual NUMA node size
 	// seen by the guest.
-	CoresPerNumaNode int32 `xml:"coresPerNumaNode,omitempty" json:"coresPerNumaNode,omitempty"`
+	CoresPerNumaNode *int32 `xml:"coresPerNumaNode" json:"coresPerNumaNode,omitempty"`
 	// Whether coresPerNode is determined automatically.
 	AutoCoresPerNumaNode *bool `xml:"autoCoresPerNumaNode" json:"autoCoresPerNumaNode,omitempty"`
 	// Whether virtual NUMA topology is exposed when CPU hotadd is