[roll] Roll fuchsia [component_manager] add built-in dispatcher component

The dispatcher component can be given configuration capabilities telling
it what capability name and type its dispatching, and the URL of a
component to dispatch to. It will expose a dynamically populated
dictionary holding the capability it dispatches. Any routing requests to
that capability will cause the dispatcher to launch a new worker
component with the given URL, and it will then forward the route request
to the worker. The worker is watched for a stop event, at which point
the worker is destroyed.

Any capabilities offered to the dispatcher are passed through to the
workers.

Original-Fixed: 415968290
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1245065
Original-Revision: ad0a94f5b7395be689e0e2a0bf9881a667025285
GitOrigin-RevId: 7ee5d21599fb0d571cf6d7bd88efbf5fa578f911
Change-Id: If885aad69548c74f9af24ffb605ea08de7a809b4
1 file changed
tree: 71aa2d6d55f85833068dca70bed634742bfb9a9e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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 in one of the communication channels documented at get involved.

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.