Nika ama-hooks e-REST ne-auth e-BigQuery PHP i-proxy handler
Nge google/cloud-bigquery 1.39.3, nika i-callable efanayo ku-httpHandler ne-authHttpHandler lapho zombili izindlela zidinga umxhumanisi.
Ama-hooks okulethwa kwe-REST kanye nesicelo se-token ku-google/cloud-bigquery 1.39.3 angabelana nge-PSR request handler eyazi i-proxy:
$proxy = 'http://proxy.example:8080';
$http = new \GuzzleHttp\Client();
$send = static function (
\Psr\Http\Message\RequestInterface $request,
array $options = []
) use ($http, $proxy) {
$options['proxy'] = $proxy;
return $http->send($request, $options);
};
$bigQuery = new \Google\Cloud\BigQuery\BigQueryClient([
'projectId' => $projectId,
'httpHandler' => $send,
'authHttpHandler' => $send,
]);I-callable ibeka inketho ye-proxy ye-Guzzle kusizo ngalunye, kuhlanganise ne-HTTP endpoint yomphakathi ekhethwe ohlwini lwe-HTTP proxy, futhi i-constructor inika leyo callable ku-httpHandler naku-authHttpHandler. Lokhu kuhlanganisa ukulethwa kwe-REST kanye nezicelo zokuqinisekisa ezisebenzisa lelo hook. Gcina ukuhlelwa kwe-credential okusekelwayo; i-credential enenye i-transport idinga ukuthi neyayo ihlolwe.
Engeza okuhlukile okuqondile okudingekayo ngokusebenzisa ukuhlelwa kwe-proxy okusekelwa yi-Guzzle. Gcina i-endpoint ye-BigQuery API njengendawo yesevisi: ukufaka ikheli le-proxy ku-apiEndpoint kukhetha enye isevisi esikhundleni sokuhlela lo mzila.
Lokhu kuyizinketho ze-constructor ze-BigQueryClient. Azihleli i-channel ye-gRPC ezimele futhi azihambisi i-Google\Client ne-interface ye-setHttpClient kumtapo wolwazi ohlukile we-Google API PHP Client.