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 was archived by the owner on Mar 6, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
Improve debug logging about the path that the authentication library is taking #472
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
When debugging what went wrong with the authentication library, it can be sometimes hard to track the path it took. For example, if it was issuing Compute Engine Metadata checks or (credential checks on a path) We've had cases in support sometimes where it would be good to understand the path that had been taken.
Describe the solution you'd like
I'm proposing (and will add a PR) to a bit more logging around:
What checks you are taking during the auth checking process
A bit more verbose output about the things that went well and what did not in those checkers
Describe alternatives you've considered
You can use the Python debugger, but this never helps after the fact. :)
Activity
busunkim96 commentedon Mar 26, 2020
Hi @hilts-vaughan that sounds great! Please tag me once you've opened a PR.
hilts-vaughan commentedon Mar 26, 2020
I opened two:
#474
#473
I tried to orchestrate the paths that I found would have been most valuables in some of the customer issues I had been debugging lately.
westarle commentedon Oct 16, 2023
I see the two PRs merged so closing this issue fixed. Feel free to reopen if there is more work to do!