Skip to content

Treat respose schemas better #1735

@gtema

Description

@gtema

Sadly responses in some services are varying with microversions so heavily that simply sticking to the latest possible does not work. It is not even possible to define the parameters (with their types) that would be always returned. Due do that we need to:

  • start populating different response schemas by the codegenerator
  • use the response type matching the MV selected for the response

Another bad thing is that even this is not easily possible to prepare a single struct for the response of a single MV. E.g., server show command since mv 2.69 defines result as a oneOf from 2 not very compatible schemas, so a way how to handle this during the code generation need to be found

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions