[roll] Roll fuchsia [security] Add platform component_tree_config This file will allow platform-defined components which use dynamic routing features to tell Scrutiny how to incorporate their capabilities into Scrutiny's model. In this current state, it enforces that code which dynamically handles capabilities be able to represent the set of capabilities in this static config file. For example, this is needed for config capabilities presented from a dynamic dictionary to successfully route for the structured config model. To soft-migrate OOT usages, this change will add a new field to represent a list of component tree configs without removing the existing single-file field. Original-Bug: b/468009955 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1446188 Original-Revision: c84911a1933f64c249fdf23dd9e8f5d95072df05 GitOrigin-RevId: f85b720824f8db77c53320b7e0755f800a82ec4d Change-Id: Id42849f05db25d545183e4973d08fb4f8d6cb1af
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.