[roll] Roll fuchsia [scrutiny] Enable scrutiny to validate dynamic dictionaries Some dictionaries may be filled at runtime, but we expect their contents to be sufficiently known from the product owner perspective. To enable validating routes which source is in a dynamic dictionary, this change extends the `component_tree_config.json5` file to include a new field which contains a mapping from (moniker, dynamic dictionary name) to the capabiliities we expect the dictionary to contain. The test case added would fail if not dynamic dictionaries were provided. Original-Bug: 382115706 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1167372 Original-Revision: 6f79c9fdc52709d0df3209945aa0469eab0c9518 GitOrigin-RevId: 48886198663c4e6539ff8d0a7f2ec0bfb86d13ab Change-Id: I40b42fd81f097bcd24ff7afa384991c0071b1001
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.