| commit | 7e0559e5d00e7bb077ed65a381071cadcf828c37 | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Fri May 24 23:41:27 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri May 24 23:41:27 2019 |
| tree | e43c2adc6f927ead20eee207f0e3436856c6c158 | |
| parent | 0cd0a900dadf7b459ee92e1e660eec65656afd76 [diff] |
[lucicfg] Add a very weak notion of "key namespaces".
A key kind can be prefixed with '@' to indicate that it represents a namespace.
Currently it affects only how the node title is converted to a string ("ns:a/b"
instead of default "ns/a/b").
Namespaces will be eventually used when loading multiple project configs into
single instance of lucicfg process.
R=tandrii@chromium.org
BUG=966603
Change-Id: Ibf8572f0c73e151ecc7311610ea152cfdd1a447f
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1628822
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@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.