[roll] Roll fuchsia [structured_config] Support transitional availability

If a config is marked as transitional, it's not an error if it's
not routed from void. This is important to allow for soft-transitions
for adding new configuration capabilities.

Add an integration test that checks that a transitional value
with no route will get the value from the CVF file.

Original-Fixed: b/315170479
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/956880
Original-Revision: d514743ecf13aacb256bd3b00344d8e14f7cb096
GitOrigin-RevId: 3587342d1d070db286ebc8d42213d48eb7b16fa9
Change-Id: Ia574d03273979e9f0f88d30fe880f7d70b8ac8b2
1 file changed
tree: ea061f05dc82db5c0a26bdf115de440ad435f4b7
  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.