Open marchof opened 2 years ago
Oh...you are right, forgot to update the README. So we switched to 3.0 and I agree it makes sense to have a lifecycle statement. Will work on that. Thanks for the heads up 👍🏻
BTW is there a accessible repository where the API is actually implemented?
I use it in the discoclient https://github.com/foojayio/discoclient
I'm not talking about the client. I'm curious about the server side implementation of the REST endpoint of the disco API.
Ah ok…only on our internal gitlab…
@HanSolo What is the reason for not publishing the source code of the project? Disco API cannot be considered open-source until the actual source is released. That makes it opaque and I'm wondering how other projects decided to rely on such API.
The production code has code in it that is bound to our internal infrastructure which is also the reason why we have it on our internal gitlab
I just noted that the swagger ui points to version 3.0. Is this already in production? The README.MD refers to 2.0 only.
As a API consumer it would be very helpful to have an lifecycle statement which lists available versions with status and EOL date.
Thx for the great work!