http_archive and http_file should be wired to support --google_default_credentials
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
### Description of the feature request:
Currently `--google_default_credentials` i.e. ADC supports only authenticating for remote cache and RBE. It doesn't use it to support downloading `http_archive` or `http_file` repositories if they are stored in a GCS bucket.
Feature request is for http_archive to also use the `--google_default_credentials` option to authenticate.
### Which category does this issue belong to?
_No response_
### What underlying problem are you trying to solve with this feature?
Support an existing way of authentication across other workflows.
### Which operating system are you running Bazel on?
_No response_
### What is the output of `bazel info release`?
_No response_
### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.
_No response_
### What's the output of `git remote get-url origin; git rev-parse HEAD` ?
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
_No response_
Contributor guide
Research direction
Start by locating the Bazel implementation and tests for http_archive, http_file, and the --google_default_credentials option. Trace how credentials are used for existing remote cache or RBE authentication, then verify that downloads from GCS work for both repository rules while unauthenticated behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, java
- Domain
- build-system, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100