[lucicfg] Start refactoring to support multiple output config sets.

Former ConfigSet struct is split into Output (ALL generated output) and
ConfigSet (a single group of configs validated as a unit). All output is still
treated as a single config set.

Also move generators registration from configset.go into its own file.

R=tandrii@chromium.org
BUG=945048

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