Closed Reintjuu closed 4 years ago
Hi,
I never test this scenario. Because I have no experience with this service.
This library generally uses Service Discovery from Ocelot. It is possible that there is only a small problem, unfortunately I have no way to find it out (I do not have a ready environment). If you had any other information that could help me, that would be nice. For example, some adition info from a given exception. It would be ideal if you could connect this project directly to yours and debug what the problem is.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.
I had the same issue and added support for Consul in my fork:https://github.com/raga70/MMLib.SwaggerForOcelot/tree/ConsulSupport
also made a pull request, so by the time you are reading this, it might already be in the main code base
With Consul up and running (available through port 8500), I'm not able to use this library to access an individual service's swagger documentation.
The Example service is configured as follows:
And my ocelot.json:
The services are accessible directly (by creating a simple API controller with a HttpGet method) but don't seem to be through swagger. I'm getting the following error in the logs: