JT Olio 946ec201e2 metainfo: move api keys to part of the request (#3069) ... What: we move api keys out of the grpc connection-level metadata on the client side and into the request protobufs directly. the server side still supports both mechanisms for backwards compatibility. Why: dRPC won't support connection-level metadata. the only thing we currently use connection-level metadata for is api keys. we need to move all information needed by a request into the request protobuf itself for drpc support. check out the .proto changes for the main details. One fun side-fact: Did you know that protobuf fields 1-15 are special and only use one byte for both the field number and type? Additionally did you know we don't use field 15 anywhere yet? So the new request header will use field 15, and should use field 15 on all protobufs going forward. Please describe the tests: all existing tests should pass Please describe the performance impact: none		2019-09-19 10:19:29 -06:00
..
grpcauth	metainfo: move api keys to part of the request (#3069)	2019-09-19 10:19:29 -06:00
apikey.go	pkg/auth: use grpc.WithPerRPCCredentials (#2670)	2019-07-31 13:57:13 +02:00