[feature] Initializing the new Go client

[JulienBreux]

[feature] Initializing the new Go client

[lbroudoux]

Hey Julien!

I love your approach, as discussed previously. The nice thing is that we just published the 1.8 OpenAPI specification for Microcks API 😉 This one can be found here: https://github.com/microcks/microcks/blob/1.8.x/api/microcks-openapi-v1.8.yaml.

From what I understand, we'd just have to use this new reference and re-generate the client but ... I can't see any reference to the 1.7 version in config files or other ... Is there some kind of discovery mechanism that just uses what's found under the /schema folder?

I've got another question regarding the versioning scheme: how can we track the matching between version the go-client version and the API version? Should we include a 1.8 info in the title to inform it was generated from the 1.8? How is this question usually handled in the Go community?

Many thanks for your contribution! Please go ahead with the PR! 👍

[JulienBreux]

From what I understand, we'd just have to use this new reference and re-generate the client but ... I can't see any reference to the 1.7 version in config files or other ... Is there some kind of discovery mechanism that just uses what's found under the /schema folder?

Yes, that's a good idea.
In fact, I have two questions to answer:

1. Are we going to use classic SEMVER or version this client like Kubernetes? (https://github.com/kubernetes/client-go?tab=readme-ov-file#compatibility-matrix)
   For Kubernetes Go client, we use go get k8s.io/[email protected] (or obviously go get k8s.io/client-go@latest.
2. Is the client multi-version compatible, or does each version of the client represent the major version of Microcks?

My idea is to have the same things:
All yaml in schema folder BUT core branch like 1.7.x, 1.8.x to distribute for each version.

I use the idea of Kubernetes to avoid reinventing the wheel!

[lbroudoux]

Awesome!!!