Ba waɗannan REST da auth hooks na BigQuery PHP proxy handler

Hooks ɗin isar da REST da buƙatar token a cikin google/cloud-bigquery 1.39.3 na iya raba PSR handler na buƙata da ke sane da 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,
]);

Callable ɗin yana sanya zaɓin proxy na Guzzle a kan kowace buƙata, ciki har da HTTP endpoint na jama'a da aka zaɓa daga jerin HTTP proxy, kuma constructor ɗin yana ba da wannan callable ga httpHandler da authHttpHandler duka. Wannan yana rufe isar da REST da buƙatun tabbatarwa da suke amfani da wannan hook. Ka riƙe saitin credential ɗin da ake tallafawa; credential da ke da wata hanyar jigilar bayanai tana buƙatar a duba wannan hanyar ita ma.

Ƙara keɓancewar kai tsaye da ake buƙata ta hanyar tsarin proxy na Guzzle da ake tallafawa. Ka riƙe BigQuery API endpoint a matsayin ƙarshen sabis ɗin: sanya adireshin proxy a cikin apiEndpoint yana zaɓar wani sabis maimakon saita wannan hanyar.

Waɗannan zaɓuɓɓukan constructor ne na BigQueryClient. Ba sa saita tashar gRPC mai zaman kanta kuma ba sa dacewa a cikin Google\Client da interface ɗin setHttpClient a cikin ɗakin karatu na Google API PHP Client daban.