Updated client.go with newer wapi version 2.7.3

[rudhron]

No description provided.

[fanatic]

Thanks for the change! For the reasons I outlined over in #33, I'm hesitant to merge this until I we can verify that it maintains backwards compatibility for the folks using this library today. The infoblox I have access to is still on the much older wapi version, and merging this pull request would break that. Perhaps it can be configurable?

[rudhron]

Thanks for reaching out Jason! Yes if it breaks your code please don't commit it. I have cloned your repo but am unable to build the binary. Do you have any specific deps for the build?

On Sun, Jul 1, 2018 at 14:08 Jason Parrott ***@***.***> wrote: Thanks for the change! For the reasons I outlined over in #33 <#33>, I'm hesitant to merge this until I we can verify that it maintains backwards compatibility for the folks using this library today. The infoblox I have access to is still on the much older wapi version, and merging this pull request would break that. Perhaps it can be configurable? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#35 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ad0Ewwfoh_ePmZv6yJMwO9XOlsoTmCkMks5uCTo3gaJpZM4U9ge7> .

-- Regards, Prithviraj Jathan

[fanatic]

You should be able to run $ go install github.com/fanatic/go-infoblox and it'll download dependencies and build the binary. Same should work for your fork. Do you have a specific error message?

[sjwl]

I have an immediate need to use the newer version WAPI, for example:

curl -k -u admin:infoblox -H "Content-Type: application/json" -X POST https://10.97.65.208/wapi/v2.5/network -d '{"network":"func:nextavailablenetwork:10.10.0.0/16,default,24","comment":"test","comment":"test","comment":"test"est"}'          19-03-26 - 15:07:29
"network/ZG5zLm5ldHdvcmskMTAuMTAuMS4wLzI0LzA:10.10.1.0/24/default"

vs

curl -k -u admin:infoblox -H "Content-Type: application/json" -X POST https://10.97.65.208/wapi/v1.4.1/network -d '{"network":"func:nextavailablenetwork:10.10.0.0/16,default,24","comment":"tes4","comment":"tes4","comment":"tes"test"}'        19-03-26 - 15:11:35
{ "Error": "AdmConProtoError: Bad value for network: 'func:nextavailablenetwork:10.10.0.0/16,default,24'", 
  "code": "Client.Ibap.Proto", 
  "text": "Bad value for network: 'func:nextavailablenetwork:10.10.0.0/16,default,24'"
}

But rather than waiting for an extensive regression test in order to support 2.x, could we instead add a new version parameter to NewClient, where the default version could still be 1.4.1? Otherwise, those who need 2.x functionality will just create forked versions replacing the hard-coded 1.4.1 to 2.7.