-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support vor netbox v3.3? #136
Comments
I can replicate this with v3.3.6 on both the v3.2 and v3.4 versions. For example, getting a device list returns:
|
I used |
I didn't see a PR for yours but it looks like someone else submitted a PR in the meantime: #137 |
this issue can be closed - I've verified #137 fixed it. |
Hello, i have tested the lastest version from "master" branch. i am still getting errors when calling "dcim.NewDcimConsolePortsListParams()", for example
in the current implementation this property is
and earlier (when it worked) it was
Is there some kind of config for the serializer to make this work? how come others dont have those serialization problems? Thank you |
I didn't try this one. |
Support added by release v3.3.10-0. |
Hello, we are using netbox version v3.3.4 at this point. I tried to use the netbox client with release "netbox_v3.2" and the prerelease "netbox_v3.4". I am facing several incompatibility issues.
json: cannot unmarshal number 35.0 into Go struct field DeviceWithConfigContext.results.position of type int64 json: cannot unmarshal number into Go struct field IPAddress.results.assigned_object of type string cannot unmarshal array into Go struct field IPAddress.results.nat_outside of type models.NestedIPAddress
There are also several unmarshalling problems where referenced objects cannot be unmarshalled to the type "map[string]*string". if its changed to "map[string]any" then its working.
are you planning to release a compatible version vor version 3.3. any time soon?
maybe you can consider the changes i made in my fork and merge them
christophbrejla/go-netbox@master...feature/netbox_v3.3
The text was updated successfully, but these errors were encountered: