fix: use gcloud creds flow if explicit file path is set to gcloud adc path #705
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If user doesn't set GOOGLE_APPLICATION_CREDENTIALS path, then project id can be obtained.
If user sets GOOGLE_APPLICATION_CREDENTIALS path to gcloud adc path, then project id can not be obtained. In this case, we should fall back to gcloud creds flow in the
google.auth._default
logic, so project id can be obtained via gcloud.