[lucicfg] Force kwargs for optional parameters in validators.

This makes it safer to change them later and makes calls more
readable.

R=iannucci@chromium.org, tandrii@chromium.org

Change-Id: I2d07471ca9076d8708b5320200086b656777db72
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2136236
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
6 files changed
tree: 02fa9d67604d52f1daeffbcaa9c3a5b3806e921a
  1. .gitallowed
  2. .gitattributes
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. OWNERS
  8. PRESUBMIT.py
  9. README.md
  10. WATCHLISTS
  11. appengine/
  12. auth/
  13. buildbucket/
  14. cipd/
  15. client/
  16. cmdrunner/
  17. codereview.settings
  18. common/
  19. config/
  20. cq/
  21. dm/
  22. examples/
  23. gce/
  24. grpc/
  25. hardcoded/
  26. led/
  27. logdog/
  28. luci_notify/
  29. lucicfg/
  30. lucictx/
  31. luciexe/
  32. machine-db/
  33. milo/
  34. mmutex/
  35. mp/
  36. resultdb/
  37. scheduler/
  38. server/
  39. starlark/
  40. swarming/
  41. tokenserver/
  42. tools/
  43. tumble/
  44. vpython/
  45. web/
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.