Use authenticated bucket requests

By default, storage clients are authenticated. In the past, we used an
anonymous client when the staging IAM did not have permissions to access
the production bucket (which was publicly accessible after all).

In the future, all requests to buckets should be authenticated so that
we can restrict public access to all project buckets.

Bug: 1257945
Change-Id: I2f872de05f83972cde5b9b5c62341c0b330c1977
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/chrome-devtools-frontend/+/3576123
Auto-Submit: Alexander Schulze <alexschulze@chromium.org>
Reviewed-by: Tamer Tas <tmrts@chromium.org>
Commit-Queue: Tamer Tas <tmrts@chromium.org>
1 file changed
tree: ccb35b892e44c858bb392aef7b3e058557701a55
  1. gae_py3/
  2. .gitignore
  3. codereview.settings
  4. OWNERS
  5. README.md
  6. WATCHLISTS
  7. whitespace.txt
README.md

This repo contains:

  • the infra for serving the devtools frontend from Google's app engine (gae_py3)

See this README and go/devtools-hosting-app for details.

go/devtools-uploader references to a deprecated version of this app.