[roll] Roll fuchsia [component_manager] Factor out shared availability transformation

This is a useful primitive that appears both in production and in
playgrounds. In doing so I also added tests since there's a deficiency
in unit tests in some capability types.

This answers the question of "should we check relative paths" in
new_forwarding_router in the negative.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/947546
Original-Revision: 769b5011f8494538565f289dbce9fbc6f2eaba1f
GitOrigin-RevId: 0b98f4ccc430980c9e440cf4029c0a1388f6ff9e
Change-Id: I672c673ed45c7351582ce5b2e8303a3a348cb3d3
1 file changed
tree: 120e172f7d21f0abe59980de2b9801fcd54a531e
  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.