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
The IP based env var is used here to ping the address of the server.
Using GCE_METADATA_IP seems to be unique to google-auth-python while other gcp sdk libraries allows you to override with just GCE_METADATA_HOST.
The usecase is if anyone wants to run a custom endpoint or local metadata emulator you'd have to know this specific environment variable just for python.
The suggestion is if a user set GCE_METADATA_HOST, just use whats there.
For backwards compatibility, if the user sets both GCE_METADATA_HOST and GCE_METADATA_IP, the behavior is the same as now.
i think one simplistic way to get to that is to alter _metadata.py as such
If users want to set a custom metadata server endpoint, you have to use both
GCE_METADATA_IP and GCE_METADATA_HOST.
The IP based env var is used here to ping the address of the server.
Using
GCE_METADATA_IP
seems to be unique to google-auth-python while other gcp sdk libraries allows you to override with justGCE_METADATA_HOST
.The usecase is if anyone wants to run a custom endpoint or local metadata emulator you'd have to know this specific environment variable just for python.
The suggestion is if a user set
GCE_METADATA_HOST
, just use whats there.For backwards compatibility, if the user sets both
GCE_METADATA_HOST
andGCE_METADATA_IP
, the behavior is the same as now.i think one simplistic way to get to that is to alter _metadata.py as such
The text was updated successfully, but these errors were encountered: