Add GetToolchainsForBoard to ToolchainService definition

BUG=b:237098403
TEST=./generate

Change-Id: I380bbbdad23b48a1c2b399af245f826fb4e732ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3732790
Reviewed-by: Benjamin Shai <bshai@google.com>
Auto-Submit: Jack Neus <jackneus@google.com>
Commit-Queue: Jack Neus <jackneus@google.com>
(cherry picked from commit 523392c2e0e2b3246890dd49591633f467f87d75)
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3752957
Commit-Queue: Madeleine Hardt <hardtmad@google.com>
Reviewed-by: Madeleine Hardt <hardtmad@google.com>
4 files changed
tree: 740844d91861235795c302c0030b3b62764f0148
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  10. generate.sh
  11. LICENSE
  12. OWNERS
  13. PRESUBMIT.cfg
  14. PRESUBMIT.py
  15. README.md
  16. setup_cipd.sh
  17. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.

When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.