-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bazel Remote Cache: Cannot use WIF-generated credentials #14278
Comments
I believe this is easy as updating the third_party libraries here: https://github.com/bazelbuild/bazel/tree/master/third_party/auth |
Facing the same issue. @kylekurz, could you find a workaround while the third-party libraries aren't updated? |
@bazaglia I've resigned myself to using a SA credential in a GitHub secret for now, with notes to remove it once this is fixed. |
Fixed by #15176. Closing. |
@coeuvre Is that change low enough risk to get into 5.2? |
I think it's safe to get into 5.2. |
Will it be part of the release? I just looked at the commits on the release's branch and I don't see it there... |
Looks like it needs to be cherry picked onto the release branch #15176 (comment) |
Yep, I saw the comment on #15210 - should I comment it as a blocker for the release? |
Getting cherry-picked here: #15383 |
Unfortunately, even though Bazel 5.2 updates the Google Auth library, something seems broken and the following Bazel command:
Fails with:
This looks related to this issue: googleapis/google-http-java-client#340 |
Description of the problem / feature request:
Bazel cannot use credentials from Workload Identity Federation, exits with error:
Feature requests: what underlying problem are you trying to solve with this feature?
Using remote cache without providing a permanent Service Account JSON credential in a secret or directly in my repository.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Set up a Google Cloud Storage bucket and configure WIF via these instructions: https://github.com/google-github-actions/auth. Once you've set it up, use the auth module to create a job that utilizes a credential file for remote cache access:
What operating system are you running Bazel on?
Ubuntu 20.04 on a GitHub Hosted Runner
What's the output of
bazel info release
?release 4.2.1
If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.N/A
What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
?N/A
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
N/A
The text was updated successfully, but these errors were encountered: