Currently the types in internal/omclient/types.go contain only the fields that have been needed so far for Vortexa's use cases. Service, Pipeline and TestCase request/response types each only expose a subset of what the OM API actually accepts and returns.
Goal
Mirror the full OM API shape in the omclient types, even for fields that are not consumed today. This way the package clearly reflects the underlying API surface and does not appear to define its own concepts.
Context
Raised in PR #3 review by @kujon.
Currently the types in
internal/omclient/types.gocontain only the fields that have been needed so far for Vortexa's use cases. Service, Pipeline and TestCase request/response types each only expose a subset of what the OM API actually accepts and returns.Goal
Mirror the full OM API shape in the omclient types, even for fields that are not consumed today. This way the package clearly reflects the underlying API surface and does not appear to define its own concepts.
Context
Raised in PR #3 review by @kujon.