Open ByteOtter opened 2 months ago
This has been addressed somewhat by implementing a workaround when generating API clients with Thanix. See https://github.com/The-Nazara-Project/Thanix/commit/7c54106807f78cfeb513635679209c1032c91a04 for more info.
The issue will stay open for now to remind us to address this again in the future.
Also, further research needs to be done on NetBox's end whether this may be an issue with their database migration problem.
After further investigation, the erroneously
null
fields in NetBox's responses to theInterface
endpoints definitely looks like this is a problem on NetBox's end.Looking at the fields
link_peers_type
andconnected_endpoints
in theInterface
struct, we can see that the schema requires them to be aString
and aVec
. Which gets translated correctly inthanix_client
. However, the application returns both of these values asnull
, which does not correspond with the schema.This leads to several conclusions:
v0.1.0
to be working with NetBoxv3.6.x
as per the decision made in #74.Backend bug hunting must also be conducted as we cannot be sure this problem is fixed with NetBox
v4.x
. I had opened an issue with NetBox about a possible bug on this end (https://github.com/netbox-community/netbox/issues/16301) they asserted that this is not an issue with them. We need to collect further information before we can proceed to report a bug again.Originally posted by @ByteOtter in https://github.com/The-Nazara-Project/Nazara/issues/73#issuecomment-2326581393