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
While mocking up data I discovered a compatibility issue. When a network interface is connected to a NAT network, it has a NAT address which we represent like this:
The network_id in this data structure is an integer. This is an inconsistency in the REST API -- the network_id of the interface itself is a string. The NetworkNatAddress struct needs to accept an integer when parsing JSON.
The text was updated successfully, but these errors were encountered:
While mocking up data I discovered a compatibility issue. When a network interface is connected to a NAT network, it has a NAT address which we represent like this:
The
network_id
in this data structure is an integer. This is an inconsistency in the REST API -- thenetwork_id
of the interface itself is a string. TheNetworkNatAddress
struct needs to accept an integer when parsing JSON.The text was updated successfully, but these errors were encountered: