Repository navigation
We should mention GOOGLE_APPLICATION_CREDENTIALS in the Authentication section. #331
Description
Activity
@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.Right, it should not be a problem to temporarily override environment variable.
- added a commit that references this issue
on Jul 14, 2022 - added 4 commits that reference this issue
on Aug 9, 2022 - added a commit that references this issue
on Feb 1, 2023 - added a commit that references this issue
on Jan 6, 2026 - added a commit that references this issue
on Jan 22, 2026 - added a commit that references this issue
on Feb 24, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 23, 2026 - added 2 commits that reference this issue
on Apr 29, 2026
The main gcloud-java README.md contains an authentication section however this section does not
mention the option of using the
GOOGLE_APPLICATION_CREDENTIALSenvironment variable to point to a key file.@mziccard I now wonder if we need the
GCLOUD_TESTS_KEYandGCLOUD_TESTS_PROJECT_IDin theRemoteGcsHelperasGOOGLE_APPLICATION_CREDENTIALScould be used instead of the former andGCLOUD_PROJECTcould be used instead of the latter.