You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The created field of all change-logged models now conveys a full datetime object, rather than only a date. (Previous date-only values will receive a timestamp of 00:00.) While this change is largely unconcerning, strictly-typed API consumers may need to be updated.
NetBox 3.2 introduced breaking changes that make this package incompatible: https://github.com/netbox-community/netbox/releases/tag/v3.2.0. This is because of a change in the created timestamp of the API.
The created field of all change-logged models now conveys a full datetime object, rather than only a date. (Previous date-only values will receive a timestamp of 00:00.) While this change is largely unconcerning, strictly-typed API consumers may need to be updated.
I run into this issue when using the Terraform NetBox provider: e-breuninger/terraform-provider-netbox#145.
I believe this is because go-netbox depends on strfmt v0.20.2, that defines
RFC3339FullDate
:https://github.com/go-openapi/strfmt/blob/v0.20.2/date.go#L39-L43
To parse instances of
"date"
.https://github.com/go-openapi/strfmt/blob/v0.20.2/format.go#L105-L109
Which is what they use to parse the created responses. So it only expects a date.
I reproduced this error in the Go playground -> https://go.dev/play/p/Kybi_Kguigf.
Thanks.
The text was updated successfully, but these errors were encountered: