-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Consul service discovery error 500 #957
Labels
bug
Identified as a potential bug
Consul
Service discovery by Consul
merged
Issue has been merged to dev and is waiting for the next release
Service Discovery
Ocelot feature: Service Discovery
Spring'24
Spring 2024 release
Milestone
Comments
Leandropintogit
pushed a commit
to Leandropintogit/Ocelot
that referenced
this issue
Oct 29, 2019
Leandropintogit
pushed a commit
to Leandropintogit/Ocelot
that referenced
this issue
Oct 29, 2019
@Leandropintogit
Please share more details! |
Duplicate of #954 |
@Leandropintogit |
raman-m
added
bug
Identified as a potential bug
Service Discovery
Ocelot feature: Service Discovery
Consul
Service discovery by Consul
Spring'24
Spring 2024 release
labels
May 15, 2024
raman-m
added a commit
that referenced
this issue
May 27, 2024
…e discovery provider (#2067) * Interfaces folder and namespace * `IConsulServiceBuilder` interface vs `ConsulServiceBuilder` class * Inject services into `ConsulServiceBuilder` * Extend `IConsulServiceBuilder` interface * Finalize design of the customization. No JSON options because `ServiceDiscoveryProvider` are generalized for all types of providers * Remove BDDfy in favor of AAA pattern * Refactor original unit tests * Rename to `DefaultConsulServiceBuilder` * Update src/Ocelot.Provider.Consul/DefaultConsulServiceBuilder.cs Update `IsValid(ServiceEntry entry)` Co-authored-by: Raynald Messié <redbird_project@yahoo.fr> * Code review by @RaynaldM * Read the node instance from `ServiceEntry`. If it is null, search for a node in the common collection. * Refactor `OcelotBuilderExtensionsTests` * The generic `AddConsul<TServiceBuilder>(IOcelotBuilder)` method * Rename to `ConsulTests` * Unit tests: 100% coverage * Move to `ServiceDiscovery` folder * DRY: GivenServiceEntry, GivenRoute * Convert to file-scoped namespace * Inherit from `Steps` * Refactor acceptance tests * Acceptance test for #954 user scenario * Move "Store Configuration in Consul" to "Service Discovery" * Feature docs --------- Co-authored-by: Raynald Messié <redbird_project@yahoo.fr>
raman-m
added
the
merged
Issue has been merged to dev and is waiting for the next release
label
May 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Identified as a potential bug
Consul
Service discovery by Consul
merged
Issue has been merged to dev and is waiting for the next release
Service Discovery
Ocelot feature: Service Discovery
Spring'24
Spring 2024 release
The issue #909 added a option to resolve hostname of consul node using its name, but the name of consul node is a arbitrary string and not always a valid hostname.
I created a new node on consul called services and registred my services in this node. when ocelot query for services, it binds service to services:9091 for example and off course, this fail.
Specifications
The text was updated successfully, but these errors were encountered: