-
Notifications
You must be signed in to change notification settings - Fork 1k
Authenticating with GOOGLE_APPLICATION_CREDENTIALS broken #8519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey @axelcarl - sorry to heat that your running into issues. I've tried to repro this on my end with a valid service account key, and I'm not seeing the same issues:
I'm surprised that the 'Running auto auth' log is not appearing in your logs. Are the logs you shared the full logs? If not, could you share the full debug log? |
Here's the full debug log:
Had to use the |
Please fix this made my IT startup have 5 hour downtime |
Hello, same here: our CI using the
Rolling back to |
Hey folks, apologies for the issue this has caused. We’ve been trying to reproduce this issue but so far we haven't been able to replicate the error. I’ve tried to replicate the issue both locally and with GitHub Actions, but no errors have been raised. Here’s the mcve, could anyone let me know if I may be missing something here? I’m getting the following debug logs when running
The above shows the ‘Running auto auth’ logs, which is similar to what @joehan observed. At the moment, it’s still difficult to determine what exactly is causing the error. Could y'all share your debug logs to help us further investigate? Could you also share your
|
Hi @aalej, thanks for investigating :) In your repro you did not use the I can easily reproduce this locally to compare the behavior of
And with the debug logs using
and using
And finally our
|
|
Ok, I think I found the root cause here - we recently added a check for whether As an immediate workaround, you can gran the Service Usage viewer role to your service account (https://cloud.google.com/service-usage/docs/access-control#serviceusage.serviceUsageViewer). I'll also make a PR shortly to make this enablement check best effort. Apologies for the inconvenience everyone! |
This should be fixed in 14.3.1, which just released. |
Uh oh!
There was an error while loading. Please reload this page.
[REQUIRED] Environment info
firebase-tools: 14.3.0
Platform: macOS & linux amd64 (gitlab ci-pipeline)
[REQUIRED] Test case
[REQUIRED] Steps to reproduce
Export valid credentials within a terminal session, then try to run
firebase use
.[REQUIRED] Expected behavior
[REQUIRED] Actual behavior
Debug output:
Confirmed that it works on
14.2.x
.The text was updated successfully, but these errors were encountered: