Skip to content
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 and http_file should be wired to support --google_default_credentials #23951

Open
udaya2899 opened this issue Oct 11, 2024 · 1 comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: feature request

Comments

@udaya2899
Copy link

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

@udaya2899
Copy link
Author

Raising this issue per conversation with @tjgq

@iancha1992 iancha1992 added the team-Remote-Exec Issues and PRs for the Execution (Remote) team label Oct 11, 2024
@oquenchil oquenchil added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed untriaged labels Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: feature request
Projects
None yet
Development

No branches or pull requests

5 participants