consul/agent/checks
Seth Hoenig 44ee818d46
grpc: use default resolver scheme for grpc dialing (#7617)
Currently checks of type gRPC will emit log messages such as,

    2020/02/12 13:48:22 [INFO] parsed scheme: ""
    2020/02/12 13:48:22 [INFO] scheme "" not registered, fallback to default scheme

Without adding full support for using custom gRPC schemes (maybe that's
right long-term path) we can just supply the default scheme as provided
by the grpc library.

Fixes https://github.com/hashicorp/consul/issues/7274
and https://github.com/hashicorp/nomad/issues/7415
2020-05-20 22:26:26 +02:00
..
alias.go Sync of OSS changes to support namespaces (#6909) 2019-12-09 21:26:41 -05:00
alias_test.go Sync of OSS changes to support namespaces (#6909) 2019-12-09 21:26:41 -05:00
check.go feat: support sending body in HTTP checks (#6602) 2020-02-10 09:27:12 -07: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-20 22:26:26 +02:00
grpc_test.go Allow users to configure either unstructured or JSON logging (#7130) 2020-01-28 17:50:41 -06:00