chromite: Remove plain failed_packages fields

Since we've migrated relevant endpoints to using a FailedPackageData
field and some time has passed, delete and reserve the fields.

BUG=b:206514844
TEST=./generate --allow-breaking

Change-Id: If8345f0041b087d8418b15f7c73d3f3215dcedfb
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3853041
Reviewed-by: Cindy Lin <xcl@google.com>
Auto-Submit: Lizzy Presland <zland@google.com>
Commit-Queue: Cindy Lin <xcl@google.com>
5 files changed
tree: 704d8f9c1dbd2ec8596181d559dffe76160dc9d3
  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.