[roll] Roll fuchsia [assembly] Support platform-declared product-provided components

Platform subsystems can declare that they support running components
that have been provided by product owners. Product owners supply their
component url, and the subsystem will tailor a core shard specifically
for them.

In this way, product owners can "hook" into the platform topology very
easily, and the platform can control the access the product component
has.

Original-Bug: b/295033962
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/957918
Original-Revision: b108552e87738305c6a5272b3bc4207cf9d72fe3
GitOrigin-RevId: ae38960de3946401c09a1bb9a547de6d512f6ef9
Change-Id: Iff1bf07b83a2764b2a6e91ca56fc87a926539bc1
1 file changed
tree: 13b9585e169da5bad709c1bb711bc036c140afbf
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.