commit | e6547ab1793085bea22cb87122981f494850cfc3 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@google.com> | Mon Nov 15 21:16:08 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Nov 15 21:16:08 2021 |
tree | 12e6f215bc5774570441ba4d2680670c215a4305 | |
parent | 37a7ebb443ce46701d147601d84c4f7ae9652454 [diff] |
Declare "role/configs.validator" binding. 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: I35b619854dea5c2cd3ff8cce041da6a321ce5cf0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3283403 Auto-Submit: Vadim Shtayura <vadimsh@google.com> Reviewed-by: Garrett Beaty <gbeaty@google.com> Commit-Queue: Garrett Beaty <gbeaty@google.com> Cr-Commit-Position: refs/branch-heads/4664@{#1064} Cr-Branched-From: 24dc4ee75e01a29d390d43c9c264372a169273a7-refs/heads/main@{#929512}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.