test_request: add new fields for CFT executions support

added new field for container metadata url. it's cleaner to have a new
field not affecting non-cft workflow. Moved run_via_cft from suite to
params. it's cleaner for params to have this info and download the metadata before invoking test_runner.

BUG=b:230909741
TEST=None

Change-Id: I06fdd9135cd94818bbfb8b37a86c2e8f50aac84a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3633000
Commit-Queue: Jared Loucks <jaredloucks@google.com>
Reviewed-by: Jared Loucks <jaredloucks@google.com>
Auto-Submit: Azizur Rahman <azrahman@google.com>
3 files changed
tree: 537dfc9872cbea12c217355667d324084f3efb47
  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.