[roll] Roll fuchsia [ffx][scrutiny] Add component tree config to structured config

Structured config extract and verify flows will route config
capabilities internally while constructing the model. To support dynamic
configuration, these flows may require the component tree config to be
supplied so the routes can be properly filled.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1445736
Original-Revision: f7e66b6f33236fc8cb3795bbd4dd6fa89d7505c2
GitOrigin-RevId: 8d4b7206637ad7b8c765344596e1f4f8bae59e08
Change-Id: Ie089f8777dd8f312163c2be03accee48630fd7fd
1 file changed
tree: 6fc012c19359846f15d90e78ecb4b59b5837ed53
  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.