tree de9a021221770328831a589998b7fb32f2a9e154
parent f3b4fc7437581683a232888df55df0f771c8093f
author Michael Mortensen <mmortensen@google.com> 1602696964 -0600
committer Commit Bot <commit-bot@chromium.org> 1609272543 +0000

Add Cloud Logging initialization based on ENV VARs and unit test.

If CHROMITE_CLOUD_LOGGING and GOOGLE_APPLICATION_CREDENTIALS are not
both set then no cros_logging is not affected for chromite clients.

I have manually verified in my own chroot that if I set
CHROMITE_CLOUD_LOGGING=1 and GOOGLE_APPLICATION_CREDENTIALS=<local.json>
where the local json file for a google-cloud-logging-enabled service account
I created in GCP then I do end up with log statements from a script run
in the chroot going to this GCP project that are visible in Google cloud
logging.

See https://cloud.google.com/docs/authentication/getting-started#cloud-console

Next step: enable these variables in staging-only, with
GOOGLE_APPLICTION_CREDENTIALS referring to a bot-based json file for the
chromebot account.  Test staging setting in CQ or with led
(go/luci-how-to-led).

BUG=chromium:1128411
TEST=manual test, pytest

Change-Id: I59d11b927fbb89b641aedb43d944918a343fccf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/2472537
Tested-by: Michael Mortensen <mmortensen@google.com>
Reviewed-by: Alex Klein <saklein@chromium.org>
Commit-Queue: Michael Mortensen <mmortensen@google.com>