[roll] Roll fuchsia [omaha-client] Avoid using system config_data in tests

It's better for the test package to hermetically include and present as
a standard directory capability anything we want to present to the
component-under-test as the config-data directory.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/841470
Original-Revision: 0c6a0efbdb29001915ff44ab978ca25d7ae79982
GitOrigin-RevId: 04328f4aa590c06dae5866aeb41872dfd3c0fcf6
Change-Id: I27a8b8078f986a0377a684f12b532cd481581ff5
1 file changed
tree: 8c74ef85e7695a1e4b9a7db2989e048d3c1eb71b
  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.