[roll] Roll fuchsia [cml] Use Config requires type

Update the Use Config fields so that it requires type
information.

If you are using a config capability you don't need
a corresponding 'config' block key, unless your
capability is optional.

If your config capability is optional, then routing
from void will cause you to receive the value in
your package's CVF file. This means we must have a
matching 'config' block key for optional values.

Original-Fixed: b/326927180
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/994677
Original-Revision: 733e94c6b4a017c7c022163f2bf0acd5b4dd21bc
GitOrigin-RevId: 64e30c2212dd0bc597863495d3783a9d2d016cae
Change-Id: Ic46534044405d92922bc589687035abea7785fbd
1 file changed
tree: 8e4f31273363861bbce21757a4bac194cbdcea8f
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.