firmware: Correct firmware updater name

The local firmware updater "updater.sh" may not always exist
(CL:3592736), so correct the updater name to the formal one,
"chromeos-firmwareupdate".

BUG=b:229686920
TEST=none

Change-Id: Ic27bf466b2ec0bdd17c5c77d5237b90f87b27372
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3637029
Reviewed-by: Jack Neus <jackneus@google.com>
Auto-Submit: Yu-Ping Wu <yupingso@chromium.org>
Commit-Queue: Yu-Ping Wu <yupingso@chromium.org>
2 files changed
tree: 3ac964aea3b84229fe94fa95614393a1137cab64
  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.