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
R=fbarchard@chromium.org
Change-Id: I26544e524cf5e900ab395ff5c440c10438723903
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/3276689
Reviewed-by: Frank Barchard <fbarchard@chromium.org>
Commit-Queue: Vadim Shtayura <vadimsh@google.com>
libyuv doesn't have its own swarming pools, so this is trivial.
Follow up will opt in libyuv to actually use realms when creating
builds.
Bug: chromium:1203285
Change-Id: Idc38be967992255cb1b852edcf114ac98df4fc5d
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/2854458
Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
