consul/command/connect
Grégoire Seux 4f62a3b528 Implement /v1/agent/health/service/<service name> endpoint (#3551)
This endpoint aggregates all checks related to <service id> on the agent
and return an appropriate http code + the string describing the worst
check.

This allows to cleanly expose service status to other component, hiding
complexity of multiple checks.
This is especially useful to use consul to feed a load balancer which
would delegate health checking to consul agent.

Exposing this endpoint on the agent is necessary to avoid a hit on
consul servers and avoid decreasing resiliency (this endpoint will work
even if there is no consul leader in the cluster).
2019-01-07 09:39:23 -05:00
..
ca Fix more unstable tests in agent and command 2018-09-12 14:49:27 +01:00
envoy connect: Fix comment DYNAMIC_DNS to LOGICAL_DNS (#4799) 2018-10-24 07:02:01 -07:00
proxy Implement /v1/agent/health/service/<service name> endpoint (#3551) 2019-01-07 09:39:23 -05:00
connect.go Original proxy and connect.Client implementation. Working end to end. 2018-06-14 09:41:56 -07:00
connect_test.go Builtin tls helper (#5078) 2018-12-19 09:22:49 +01:00