terraform-provider-nsxt
terraform-provider-nsxt copied to clipboard
tools: fix policy generation script
for avoid nsxt/resource_nsxt_policy_mac_discovery_profile.go:135:21: not enough arguments in call to client.Patch have (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt-gm/model.MacDiscoveryProfile) want (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt-gm/model.MacDiscoveryProfile, *bool) nsxt/resource_nsxt_policy_mac_discovery_profile.go:138:21: not enough arguments in call to client.Patch have (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt/model.MacDiscoveryProfile) want (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt/model.MacDiscoveryProfile, *bool) nsxt/resource_nsxt_policy_mac_discovery_profile.go:240:25: not enough arguments in call to client.Update have (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt-gm/model.MacDiscoveryProfile) want (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt-gm/model.MacDiscoveryProfile, *bool) nsxt/resource_nsxt_policy_mac_discovery_profile.go:243:25: not enough arguments in call to client.Update have (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt/model.MacDiscoveryProfile) want (string, github.com/vmware/vsphere-automation-sdk-go/services/nsxt/model.MacDiscoveryProfile, *bool) nsxt/resource_nsxt_policy_mac_discovery_profile.go:262:22: not enough arguments in call to client.Delete have (string)
@alagoutte, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]>
to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.
- Commit c10533e1e70f0857382bb3eb7345a4601dbc105f must be signed by [email protected]
hi @annakhm can you look ?
@annakhm any news about this change ?
Any news ?
Hi @alagoutte, sorry for delayed response. There a more changes that need to be made for generation scripts, for example change NewDefault<!RESOURCE!>sClient(connector)
to New<!RESOURCE!>sClient(connector)
Also, I think boolFalse
change is not global for every client.
I think the best way to adjust generation scripts to the latest SDK, and test those adjustments, would be to create a new resource with the script.
Hi @alagoutte, sorry for delayed response. There a more changes that need to be made for generation scripts, for example change
NewDefault<!RESOURCE!>sClient(connector)
toNew<!RESOURCE!>sClient(connector)
Also, I thinkboolFalse
change is not global for every client. I think the best way to adjust generation scripts to the latest SDK, and test those adjustments, would be to create a new resource with the script.
Ok I will update when create a new ressource !
This pull request for the provider is rather stale - should it move forward, be closed, or marked as draft?
Ryan Johnson Senior Staff Solutions Architect | Product Engineering @ VMware, Inc.