An API response that returned an 'opaque' had caused some issues as that
is not a response type understood by the Swagger v2 spec. This now
responds with an "object" type in place of "opaque".
It isn't entirely accurate as the opaque type could return any type, but
the Swagger v2+ spec does not allow this. See here for more information on
this. The ability to have multiple response types for a single response code
has been added as a feature in OpenAPI v3+, but this currently uses the
Swagger v2 specification.
An API response that returned an 'opaque' had caused some issues as that is not a response type understood by the Swagger v2 spec. This now responds with an "object" type in place of "opaque".
It isn't entirely accurate as the opaque type could return any type, but the Swagger v2+ spec does not allow this. See here for more information on this. The ability to have multiple response types for a single response code has been added as a feature in OpenAPI v3+, but this currently uses the Swagger v2 specification.
Signed-off-by: J.R. Garcia jrg@vmware.com