OpenAPI Spec is broken in various ways

1

The OpenAPI Spec is broken in a few ways and does not handle all cases returned by the server. So far, I’ve found:

fly.MachineConfig: this can sometimes be nullable as returned by the server, breaking clients
autostop: The enums here are of mixed type – it can have both strings and bools, breaking clients when the server sends a bool for this field.

I’ve fixed this locally, but I’m concerned this API is unsupported, which is concerning for the platform as a whole. Are there any updates on this API and it’s expansion/testing/usage?

Thanks!

1 Like
2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.