| commit | 583d93c146cb0cce6785f40be89f33d7a7cb875a | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Thu Nov 29 22:49:46 2018 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Nov 29 22:49:46 2018 |
| tree | fd38c8f10c2fcdbd55a615bdba88a29480b61070 | |
| parent | 8dbbd471c4ba648397b7b44423a33503ec463b4d [diff] |
[lucicfg] Low-level API for generating arbitrary configs. This is an escape hatch for cases when a high-level declarative API is not sufficient. It will also be used internally by the high-level generator itself. Config generating functions are registered as callbacks to allow high-level configs to be defined in a declarative way, where order of definitions is not important, as long as the entire high-level config is consistent. To allow this, we should execute all top-level Starlark code before doing any evaluation of the state, thus a necessity for delaying generator calls via callbacks. R=iannucci@chromium.org, nodir@chromium.org BUG=833946 Change-Id: Ib62640a316fc1255de873defc521be7cf67665bd Reviewed-on: https://chromium-review.googlesource.com/c/1352371 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
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 uses the same flow as Chromium contributions.