90eb5aa292
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: Iec55d5e4ea7325406a1f3dd1f9fef598ec5ad29a Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/69181 Auto-Submit: Vadim Shtayura <vadimsh@google.com> Kokoro: Kokoro <noreply+kokoro@google.com> Reviewed-by: Ben Clayton <bclayton@google.com> Reviewed-by: Ryan Harrison <rharrison@chromium.org> Commit-Queue: Ryan Harrison <rharrison@chromium.org> |
||
---|---|---|
.. | ||
commit-queue.cfg | ||
cr-buildbucket.cfg | ||
luci-logdog.cfg | ||
luci-milo.cfg | ||
luci-scheduler.cfg | ||
project.cfg | ||
realms.cfg |