consul/agent/checks
Pierre Souchay 621862606e checks: when a service does not exists in an alias, consider it failing (#7384)
In current implementation of Consul, check alias cannot determine
if a service exists or not. Because a service without any check
is semantically considered as passing, so when no healthchecks
are found for an agent, the check was considered as passing.

But this make little sense as the current implementation does not
make any difference between:
 * a non-existing service (passing)
 * a service without any check (passing as well)

In order to make it work, we have to ensure that when a check did
not find any healthcheck, the service does indeed exists. If it
does not, lets consider the check as failing.
2020-06-04 12:51:23 +00:00
..
alias.go checks: when a service does not exists in an alias, consider it failing (#7384) 2020-06-04 12:51:23 +00:00
alias_test.go checks: when a service does not exists in an alias, consider it failing (#7384) 2020-06-04 12:51:23 +00:00
check.go checks: when a service does not exists in an alias, consider it failing (#7384) 2020-06-04 12:51:23 +00:00
check_test.go feat: support sending body in HTTP checks (#6602) 2020-02-10 09:27:12 -07:00
docker.go Sets tty in docker client back to true, as a potential fix for docker exec weirdness 2017-11-05 09:44:55 -06:00
docker_unix.go Decouple the code that executes checks from the agent 2017-10-25 11:18:07 +02:00
docker_windows.go Decouple the code that executes checks from the agent 2017-10-25 11:18:07 +02:00
grpc.go grpc: use default resolver scheme for grpc dialing (#7617) 2020-05-21 17:01:47 +00:00
grpc_test.go Allow users to configure either unstructured or JSON logging (#7130) 2020-01-28 17:50:41 -06:00