diff options
author | Jakob Buchgraber <buchgr@google.com> | 2017-12-20 10:13:23 -0800 |
---|---|---|
committer | Copybara-Service <copybara-piper@google.com> | 2017-12-20 10:41:39 -0800 |
commit | 8a7c63e76320b1ae8eafc1a44d82d1214e1bfdb0 (patch) | |
tree | c29389efa25f8ce028f60596388e4fcbe91aa7ed /site/docs/build-event-protocol.md | |
parent | a982168020216055b1cc7a2825d459f76208a733 (diff) |
remote: rename auth flags.
--auth_* flags only work with Google Cloud Authentication. That's
confusing and restricts the naming of more general purpose authentication
flags that we might want to add in the future. So instead of --auth_*
let's call them --google_* (the old ones will continue working for a
while).
Also, --auth_enabled (aka --google_default_credentials) is no longer required
when specifying --auth_credentials (aka --google_credentials).
So now there's two simple ways to authenticate with Google Cloud:
* bazel build --google_default_credentials
* bazel build --google_credentials=creds.json
RELNOTES: --auth_* flags were renamed to --google_* flags. The old names
will continue to work for this release but will be removed in the next
release.
Change-Id: Ia1736f32e15a37995be3172cd9608d518ddeab44
PiperOrigin-RevId: 179700832
Diffstat (limited to 'site/docs/build-event-protocol.md')
-rw-r--r-- | site/docs/build-event-protocol.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/site/docs/build-event-protocol.md b/site/docs/build-event-protocol.md index d6163b2137..755600fa0e 100644 --- a/site/docs/build-event-protocol.md +++ b/site/docs/build-event-protocol.md @@ -209,9 +209,9 @@ these flags are also used for Bazel’s Remote Execution. This implies that the Build Event Service and Remote Execution Endpoints need to share the same authentication and TLS infrastructure. -* `--auth_credentials` -* `--[no]auth_enabled` -* `--auth_scope` +* `--[no]google_default_credentials` +* `--google_credentials` +* `--google_auth_scopes` * `--tls_certificate` * `--[no]tls_enabled` |