[logdog] add CloudLoggingConfig proto

The following names were considered, but seem too verbose or ambiguous
- CloudLoggingExporterConfig
- CloudLogging

Bug: 1164124
Change-Id: I5e3947f0beb0ce68b7703d4c68e98a82d2f399d7
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2728561
Commit-Queue: Scott Lee <ddoman@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
4 files changed
tree: 294425a72fba6f2ff83f2be247cc5f6eb69bdbd1
  1. appengine/
  2. auth/
  3. buildbucket/
  4. casviewer/
  5. cipd/
  6. client/
  7. cmdrunner/
  8. common/
  9. config/
  10. cq/
  11. cv/
  12. dm/
  13. examples/
  14. gae/
  15. gce/
  16. grpc/
  17. hardcoded/
  18. led/
  19. logdog/
  20. luci_notify/
  21. lucicfg/
  22. lucictx/
  23. luciexe/
  24. machine-db/
  25. milo/
  26. mmutex/
  27. mp/
  28. resultdb/
  29. scheduler/
  30. server/
  31. starlark/
  32. swarming/
  33. tokenserver/
  34. tools/
  35. tumble/
  36. vpython/
  37. web/
  38. .gitallowed
  39. .gitattributes
  40. .gitignore
  41. AUTHORS
  42. codereview.settings
  43. CONTRIBUTING.md
  44. CONTRIBUTORS
  45. LICENSE
  46. OWNERS
  47. PRESUBMIT.py
  48. README.md
  49. WATCHLISTS
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

Contributing

Contributing uses the same flow as Chromium contributions.