[lucicfg] Allow to populate some lucicfg.var(...) values via CLI flags.

Together with `-emit-to-stdout` this allows to use lucicfg scripts as sort-of
functions pluggable into e.g. bash scripts.

R=tandrii@chromium.org
BUG=1016462

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