-
Notifications
You must be signed in to change notification settings - Fork 512
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
Authenticaton warning when using application default credentials #594
Comments
Hi @jorob16 This is correct and this is just a warning. We emit a warning when there are no credentials set by the |
Here's what "just a warning" looks like for anyone hoping to use It would be nice if there were a way to disable this message because it drowns out actual actionable information by desensitizing anyone from paying attention to the warning output. |
I tend to treat warnings as something that shouldn't be ignored, and in many cases I treat them as errors. It would be beneficial if we were able to disable the warning. I do not use the |
Addresses google-github-actions#594 by not throwing 'No authentication' warning when using application default credentials.
Addresses google-github-actions#594 by not throwing 'No authentication' warning when using application default credentials.
Addresses google-github-actions#594 by not throwing 'No authentication' warning when using application default credentials.
Addresses google-github-actions#594 by not throwing 'No authentication' warning when using application default credentials.
TL;DR
I'm running a self-hosted GitHub Actions runner on a GKE cluster. Permissions are handled through application default credentials (Workload Identity) and my workflow works correctly (no authorization errors). Unfortunately
setup-gcloud
still spits out a warning:**Warning**: No authentication found for gcloud, authenticate with
google-github-actions/auth.
Expected behavior
I did not expect a warning, considering that the workflow works correctly and interacts with multiple GCP services for which authorization is definitely required.
Observed behavior
An authentication warning is displayed in the workflow logs and as an annotation under the job overview.
Action YAML
Log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: