Can't create a VRF Metal Gateway

[ctreatma]

When I use this SDK to create a VRF Metal Gateway, the gateway is created but I get an error that the response is not valid:

Error when calling `MetalGatewaysApi.CreateMetalGateway`: data matches more than one schema in oneOf(FindMetalGatewayById200Response)

This is happening because a VRF Metal Gateway matches both the MetalGateway.yaml schema and the VrfMetalGateway.yaml schema. In order to avoid this error, either the VrfMetalGateway and MetalGateway schemas need to be collapsed into a single schema that represents both types, or the MetalGateway schema has to be updated so that a VRF Metal Gateway is not a valid example of that schema.

[ctreatma]

In metal-java, this was done by setting additionalProperties: false on the MetalGateway schema, but this means that if non-VRF Metal Gateways ever gain a new property, existing SDKs will fail to validate new API responses. One alternative would be to add an invalid property specification to MetalGateway (for example, declaring vrf as an integer) so that a valid VRF gateway will not match that schema.

[ctreatma]

Note: the model name FindMetalGatewayById200Response is also a problem; the oneOf construct for Metal Gateways is duplicated inline in a few places in the spec, and should be extracted to a named component to simplify the generated code.

[ctreatma]

This can be worked around by adding include=ip_reservation on all requests for Metal Gateways. The IP reservation schemas have clear, reliable type differentiation, and we can leverage that to distinguish Metal Gateway types, at least until the API includes an attribute or attributes to Metal Gateways that can be used to more directly determine types.

[ctreatma]

This repo is deprecated. A corresponding issue has been created on the equinix-sdk-go repo, which replaces this one: equinix/equinix-sdk-go#64