[lucicfg] Add support for luci-config, logdog and buildbucket ACLs.

ACLs can be defined either on a project or on a bucket levels. ACLs defined on
the project level are inherited by all buckets.

Additionally, some ACLs (such as PROJECT_CONFIGS_READER, LOGDOG_*) can be
defined only on the project level, since LUCI doesn't support defining them on
a bucket level yet or they make no sense when defined on a bucket level.

R=nodir@chromium.org, iannucci@chromium.org
BUG=833946

Change-Id: Ib6175cb2cdc83aae7300c5e2a731882f6ecc4430
Reviewed-on: https://chromium-review.googlesource.com/c/1370612
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 files changed
tree: 7cc81bcdbe617d0b7934f3a8780dc914d4f1ff61
  1. appengine/
  2. auth/
  3. buildbucket/
  4. cipd/
  5. client/
  6. common/
  7. config/
  8. dm/
  9. examples/
  10. gce/
  11. grpc/
  12. hardcoded/
  13. infra/
  14. logdog/
  15. luci_notify/
  16. lucicfg/
  17. lucictx/
  18. machine-db/
  19. milo/
  20. mmutex/
  21. mp/
  22. scheduler/
  23. scripts/
  24. server/
  25. starlark/
  26. tokenserver/
  27. tools/
  28. tumble/
  29. vpython/
  30. web/
  31. .travis.yml
  32. AUTHORS
  33. codereview.settings
  34. CONTRIBUTING.md
  35. CONTRIBUTORS
  36. LICENSE
  37. OWNERS
  38. pre-commit-go.yml
  39. PRESUBMIT.py
  40. README.md
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.