12e51f6efa
It defines who is allowed to call LUCI Config validation API to validate this LUCI project's configs. This is usually done by presubmit jobs, and thus configs.validator role is assigned to try job task accounts. Previously this ACL was defined in the global "config-validation" group. It is deprecated and being replaced with per-project ACLs defined in per-project configs (like in this CL). There's still a global ACL to allow any googler to call the validation API in any LUCI project they are allowed to see. Thus the per-project binding applies only to service accounts (they are not googlers). Note: this CL was generated semi-automatically and reviewers are picked automatically based on OWNERS file. BUG=chromium:1068817 Change-Id: I57dec27982676553e40ad5dbae2b4642bb3bc935 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/69180 Auto-Submit: Vadim Shtayura <vadimsh@google.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org> |
||
---|---|---|
.. | ||
commit-queue.cfg | ||
cr-buildbucket.cfg | ||
luci-logdog.cfg | ||
luci-milo.cfg | ||
luci-scheduler.cfg | ||
project.cfg | ||
realms.cfg |