Add support for OpenAPI 3 schema change in Netbox 4.x

[nepomucen]

What does this change resolves ?

• it backports fix from fbreckle/go-netbox to enable support for Netbox 4.x:
• fixes the following error in go-netbox REST API call to dcim_devices_retrieve resource in Netbox
• tested with Netbox v4.1.11 version

Error: json: cannot unmarshal object into Go struct field NestedIPAddress.results.primary_ip.family of type int64

[smutel]

Hello,

Thank you for your PR. Unfortunately I will not continue to maintain this repo.

For the story:

• Since Netbox 4.x use openapi and not swagger, I tried to rollback my code to use the go-netbox provided by the community https://github.com/netbox-community/go-netbox. However this repo is not really maintained... PR opened since Nov 15th 2024 : Fix choices count netbox-community/go-netbox#191
• So I decided to fork again this repo and create my own lib : https://github.com/smutel/go-netbox-community. You can try the branch called work to test the last version
• This library is developed with the migration of my netbox provider to use openapi : https://github.com/smutel/terraform-provider-netbox/tree/UpdateForNetbox4

I don't how you use this lib but if you can try go-netbox-community and tell me if you encounter issues, it will be great ...

[nepomucen]

Hello, thank you @smutel for your reply.

To be honest, I'm not a Go expert, and I already failed the very first step to test run your new provider version from UpdateForNetbox4 branch - it failed to build. I spent some time troubleshooting it, but wasn't able to fix it, and I gave up eventually.

Just a side comment. I noticed also that the same API calls to Netbox through json data source very often end up now in "context: deadline exceeded" error (always at 30 sec), since I upgraded my Netbox installation to v4.1.11 version. Bit weird, and suggests me rather a performance degradation of the new Netbox version with comparison to 3.4 baseline. Terraform docs warns about such a possibility here.

I studied your provider's source code a bit, and it looks like the timeout error I hit, correlates with fixed one in go-openapi/runtime/client package.

[smutel]

Replace by #63