-
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
http_archive should support authentication #7770
Comments
+1. I think this should integrate well with Bazel's existing authentication mechanisms. |
@dkelmer BES and Remote Execution support --google_* authentication flags and soon --aws_* authentication flags. We also have a common abstraction that ideally remote repos would utilize: https://source.bazel.build/bazel/+/master:src/main/java/com/google/devtools/build/lib/runtime/AuthHeadersProvider.java?q=AuthHeadersProvider.java |
Related #9327 |
What's left to do here? |
We keep third party deps in a GCS bucket. What options for authenticating do we have? It's not clear to me that |
See #15013. We are planning to add credential helper support to |
Deduplicating against #15013. |
Description of the problem / feature request:
http_archive should support retrieving resources which require authentication
Feature requests: what underlying problem are you trying to solve with this feature?
I want to use http_archive to download tar.gz from a private github repository since from our benchmarks this is ~25% faster than using git_repository with shallow-since (we use a specific commit)
Our suggestion is to use the popular
netrc
format and havehttp_archive
read it (if exists and indicated that its usage is desired) and use it to authenticate (basically build the relevant authentication header).Any other information, logs, or outputs that you want to share?
this was discussed with @aehlig and @dslomov which agreed http_archive should support authentication
The text was updated successfully, but these errors were encountered: