featured: Add HandleSeedFetched dbus method

Add HandleSeedFetched dbus method to featured. This method will be
called by Chrome to send safe seeds used for early platform finch
disastery recovery.

BUG=b:264561345
TEST=unit tests

Change-Id: Ib7cf932bc48e64a1448d96bf416c9be2bfa20492
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/4137206
Reviewed-by: Miriam Zimmerman <mutexlox@chromium.org>
Tested-by: Kendrake Tsui <kendraketsui@google.com>
Commit-Queue: Kendrake Tsui <kendraketsui@google.com>
NOKEYCHECK=True
GitOrigin-RevId: 7d409268f1f6b6f95384c287023481bfbd5888dc
1 file changed
tree: 5693e62c4a99bf3b01e7d6d389a76b127ef0c455
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. DIR_METADATA
  11. LICENSE
  12. OWNERS
  13. README.md
  14. system_api.pc
README.md

This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.

This directory is only for things like headers and .proto files. No implementation should be added.

When writting a .proto file make sure to use:

option optimize_for = LITE_RUNTIME;

This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.

When declaring a protobuf, avoid use of required unless it is exactly what you mean. "Required is Forever" and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.