Ask questions and see you at July, 5th, 8.PM. CET: https://youtu.be/4Eh1aKc5SS4
Also checkout recent episode:
Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions. Upcoming airhacks.tv events are also going to be announced at meetup.com/airhacks
Hello Adam,
I'm using smallrye-openapi to generate the api documentation from the source code in my projects, and I'm looking for some guidance.
I'm developing a service platform which is compose of various independent components (backends), each one of them provide its own openapi definition file generated with quarkus and the smallrye openapi dependency.
Now I'm looking for a system to provide this documentation to users as a whole automatically, and while looking for libraries that merge openapi definitions I've found some npm libraries that kind of achieve that, but I found no system that could do that with the actual components at runtime.
What I'm looking for its a system similar to swagger that when is deployed reads the openapi defintions from a list of openapi endpoints and merge them to be published. ¿Do you know any software or library which can help my to do this? I've seen that with swagger it is possible to read from various servers, generating independent entries for each one, but I would like to have the documentation all together and hide the details of what services we have behind.
I think that this could be quite convenient specially in could deployments in kubernetes at lest within the scope of a namespace.
¿How do you normally tackle the api documentation?.
Thanks