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 }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
Does the comment suggest that applications should keep the global tokeninfo URL in them and use the local one only when TOKENINFO_URL is set? Or should the script fallback to tokeninfo_url if the healthcheck fails?
The text was updated successfully, but these errors were encountered:
Background: I had an incident that an instance started with an unhealthy local planb tokeninfo. The application was not using TOKENINFO_URL env variable, and the fallback to a global one didn't kick in. I am thinking of how to improve it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A comment suggests that the global tokeninfo should be used when the local healthcheck fails. However, TOKENINFO_URL doesn't seem to be set to the global one when the healthcheck fails.
Does the comment suggest that applications should keep the global tokeninfo URL in them and use the local one only when
TOKENINFO_URL
is set? Or should the script fallback totokeninfo_url
if the healthcheck fails?The text was updated successfully, but these errors were encountered: