You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
We should mention GOOGLE_APPLICATION_CREDENTIALS in the Authentication section. #331
The main gcloud-java README.md contains an authentication section however this section does not
mention the option of using the GOOGLE_APPLICATION_CREDENTIALS environment variable to point to a key file.
@mziccard I now wonder if we need the GCLOUD_TESTS_KEY and GCLOUD_TESTS_PROJECT_ID in the RemoteGcsHelper as GOOGLE_APPLICATION_CREDENTIALS could be used instead of the former and GCLOUD_PROJECT could be used instead of the latter.
@aozarov When I introduced those 2 variables I took inspiration from gcloud-node. The rationale is that to run integration tests the user must know what he is doing and he has to pick the right credentials/projectId before running tests as he is going to be billed for them.
For instance I have a personal account on Google Cloud whose credentials are set in GOOGLE_APPLICATION_CREDENTIALS but I use different whitelisted credentials/project to run integration tests.
Activity
mziccard commentedon Nov 6, 2015
@aozarov When I introduced those 2 variables I took inspiration from gcloud-node. The rationale is that to run integration tests the user must know what he is doing and he has to pick the right credentials/projectId before running tests as he is going to be billed for them.
For instance I have a personal account on Google Cloud whose credentials are set in
GOOGLE_APPLICATION_CREDENTIALSbut I use different whitelisted credentials/project to run integration tests.jgeewax commentedon Nov 6, 2015
I'm with @aozarov on this one -- having separate env vars for tests seems a
bit off.
Running tests should look something like
$ cat run_test.sh GOOGLE_APPLICATION_CREDENTIALS=test.json mvn testright?
aozarov commentedon Nov 6, 2015
Right, it should not be a problem to temporarily override environment variable.
aozarov commentedon Nov 6, 2015
I created #335 for tracking the
RemoteGcsHelperspecific keys issue.chore: release 0.118.6 (googleapis#331)
chore: release 2.1.0 (#331)
chore(main): release 2.3.2-SNAPSHOT (#331)
deps: update dependency com.google.cloud:google-cloud-shared-dependen…
deps: update dependency com.google.cloud:google-cloud-shared-dependen…
chore(main): release 3.7.2 (#334)
chore(main): release 2.3.8 (#340)
chore(main): release 1.3.2-SNAPSHOT (#331)
test(deps): update dependency junit:junit to v4.13.2 (#331)
build(java): update autorelease script (#331)
feat: allow arbitrary additional claims for JwtClaims (#331)
feat: allow arbitrary additional claims for JwtClaims (#331)
build(deps): update dependency com.google.cloud:google-cloud-shared-c…
chore: release 1.108.3 (#331)
chore: release 1.108.3 (#331)
chore: turn on renovate-bot master issue for java repos (googleapis#331)