Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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 · 0 comments
Open

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

qiangboy opened this issue Apr 10, 2024 · 0 comments
Assignees
@Burgyn

Comments

@qiangboy
Copy link

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:

  1. Original downstream swagger.json.
  2. Ocelot ReRoutes configuration.
@qiangboy 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Burgyn Burgyn

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Burgyn @qiangboy