feat: honor NO_GCE_CHECK
environment variable
#1610
+27
−0
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.
Currently,
google.auth.default()
always attempts to authenticate using the Google Compute Engine (GCE) metadata service as a fallback. There is no easy way to prevent this behavior, leading to unnecessary delays and unhelpful exceptions, particularly in cases where GCE-based authentication is pointless or undesired.This pull request introduces a
NO_GCE_CHECK
environment variable, allowing users to explicitly skip GCE metadata service authentication. This implementation mirrorsNO_GCE_CHECK
in googleapis/google-auth-library-java:Note
Other clouds also provide similar environment variables, such as
AWS_EC2_METADATA_DISABLED
on AWS.This change is also tangentially related to the following pull requests: