tree f51c7d2aeff8caef7c8225e758e9fcb8f92607f9
parent 0a6612bcb3537ee8d696fc3b9e2668b818fb07db
author Jean de Klerk <deklerk@google.com> 1545183939 -0800
committer GitHub <noreply@github.com> 1545183939 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJcGaLDCRBK7hj4Ov3rIwAAdHIIAH7gttFGvrGfnyhpXnA0ZxQh
 PGz3G0Adn54JsmSX4AIDhfXUmjQfzV79oEyHH1fj5sfJaEDtFspd13u79zEncXtU
 1AURyRwiht0zw8AW5lpp4Yr+IhnkUY0DYGeaw43ZC/bJRo72mm2kDDpQQVhnPi9D
 K0AoTlMgvU9SVDm0/5P6LfAI87VYowztiWGOrrMBPJKNXG+SnoMaJxUCEhtKt1Uy
 HhCV0EbImB7EGdjbmyqJwngNi7ugL9PG+Z0ms5PtWu/tpuoRoGIcGC99CJWuAQZr
 h84VYhYWKkwMyy2AF8EEa1hbTQ9k1bGGK2crvcTO6gmKDH5ehuyYu+zQS/cArak=
 =aXxe
 -----END PGP SIGNATURE-----
 

never retry permanent connection errors (#73)

Now that https://github.com/grpc/grpc-go/pull/2508 is in, gRPC plumbs the
last connection error when we attempt to make an RPC on a clientconn that has
not been successfully conencted.

So, in this CL, we check errors for a permanent connection problem.
Specifically if certificates are misconfigured, or ca-certificates are missing,
we expect not to be able to establish a connection in a reasonable amount of
time and instead bail out and return the error to the user to fix.

Fixes https://github.com/googleapis/google-cloud-go/issues/1234