New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Centralized API Documentation #108
Comments
Hi, This is an interesting feature, but we don't consider it as a a top priority, as this will require to change the behaviour of the official swagger-ui jars.
|
Or Zuul, or Kubernetes, etc.
That's the part of question. How to? |
Hi @octopus-prime, Its now possible to agregate multiple OpenAPI definitions using springdoc-openapi. |
@bnasslahsen I noticed that it is a spring-cloud-gateway implementation, have you ever thought about zuul? |
springdoc is about the integration with spring. There is nothing different about using spring-cloud-gateway and a spring-boot application... The integration principle should be the same with between spring-cloud-gateway and Zuul.. Note that Zuul, is now deprecated and most of projects using zuul, migrate to spring-cloud-gateway... |
Hello, Zuul and Eureka are just service-discovery products like other ones, as stated by @octopus-prime , so if you want to use it with Kubernetes (as my case) you are free to do. The problem is another one: springdoc-openapi is very powerful but unfortunately, it relies on swagger UI for the presentation part, instead of having its own. So, as for now, it is basically impossible to provide another implementation of springfox.documentation.swagger.web.SwaggerResource & For now, we have to make it work this way, waiting for the team to upgrade:
So, when will this improvement be available? Thanks |
This works for me:
application.properties
swagger-config.json sample
|
A simpler solution based on the reply from @danielgatis-mb using spring cloud discovery abstraction:
|
Assume more than one micro-service, all implemeting APIs and providing a swagger-ui.
To access all this API documentation from a single URL, a solution can be implemented using the SpringFox library.
See https://dzone.com/articles/centralized-documentation-in-microservice-spring-b
As you can see the implementation uses the classes
which of course are not provided by spingdoc.
So how can i achieve this goal with springdoc?
The text was updated successfully, but these errors were encountered: