Repository navigation
Proxy support? #1247
Description
Activity
I'm currently evaluating for the company I work for if it would make sense to run our CI's Espresso tests using Firebase Test Lab instead of using the standard Android Emulator on our local build servers.
This issue is blocking us because FTL doesn't provide any sharding feature and Flank is the best solution out there but cannot be used because of the missing proxy support ofgoogle-api-client.- addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Mar 26, 2019 - addedtype: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.and removed🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
on Apr 11, 2019 I'm also having similar issues because i'm behind a corporate proxy with a self signed certificate. The proxy url and port can be specified with VM options (
-Dhttp.proxyHost=...-Dhttp.proxyPort=...).The big problem is the self signed certificate. The
google-api-java-clientuses it's own Java KeyStore (src/main/resources/com/google/api/client/googleapis/google.jks) and not the official from Java ($JAVA_HOME/jre/lib/security/cacerts). So our self signed certificate cannot be verified and the request will fail.Writing a custom pluggable transport is also not possible since i'm not using the
google-api-java-clientdirectly. I'm using Apache Beam v2.16.0 which usesgoogle-api-java-client1.27.0 to stage files. The workaround that i come up with was to add our self signed certificate to thegoogle.jksfile located ingoogle-api-client-1.27.0.jarwhich is of course not a good solution. But then everything worked behind our proxy.
Also the Magnitude Simba drivers for BigQuery are not working for the same reason behind our proxy. They are needed so BigQuery can be used with JetBrains DataGrip.The same problems are also described in #1114 but with no solution. So is anyone working on this problem?
Reacted by Dr. Fabien Tarrade and Andrew Wood
I'm using the Firebase Test Lab Java client which uses
google-api-java-clientunder the hood. A bug report came in that the API calls aren't respecting proxies. When using the gcloud CLI, proxy support is automatically detected with no end user configuration. Is it possible to achive something similar withgoogle-api-java-client?Environment details
macOS Mojave 10.14.31.8.0_192google-api-client-1.28.0.jarSteps to reproduce
Stacktrace
External references such as API reference guides used