You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the Consul service discovery, it was found that the request path in the gateway swagger document does not have the "KeyToPath" property attached
#293
Open
qiangboy opened this issue
Apr 10, 2024
· 1 comment
Expected behavior
I found that there is a line of code in the source code SwaggerForOcelotMiddleware.cs that reads "if (SwaggerServiceDiscoveryProvider. ServiceProviderType!=" Consul ")". Why is this?
To Reproduce
If it is a possible attache:
Original downstream swagger.json.
Ocelot ReRoutes configuration.
The text was updated successfully, but these errors were encountered:
qiangboy
changed the title
Using the Consul service discovery, it was found that the request path in the gateway swagger document does not have the "KeyToPath" attribute attached
Using the Consul service discovery, it was found that the request path in the gateway swagger document does not have the "KeyToPath" property attached
Apr 10, 2024
Im having the same issue. When using Consul with service discovery, the lib is not updating the endpoints to match the upstream template. If I remove the condition:
Describe the bug
As stated in the title.
Expected behavior
I found that there is a line of code in the source code SwaggerForOcelotMiddleware.cs that reads "if (SwaggerServiceDiscoveryProvider. ServiceProviderType!=" Consul ")". Why is this?
To Reproduce
If it is a possible attache:
swagger.json
.The text was updated successfully, but these errors were encountered: