[roll] Roll fuchsia [audio_core] audio_core gets configuration directly from its package

The audio_core component now sources its configuration file(s) directly
from within its own package, continuing to surface them at `config/data` as before
to preserve compatibility with tests that create JSON files to specify custom
config_data.

This is CL 2 of 3 in a soft transition.  The previous CL added the
audio_core_config() targets to each audio_core_package() target in
preparation for this change.

config_data() targets are invisible to packages, and resource() targets
are invisible to the config_data collection mechanism, so this swap
becomes atomic.

Original-Bug: b/394133400
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1199685
Original-Revision: e0397d9c924f0e9e065fff1a6c39fb1c9264e9a6
GitOrigin-RevId: 7e5bb1e83020d571c47e3a6ba4a7c245b6e27059
Change-Id: Ief43161d57964d0b410b9e43e0054702ad132978
1 file changed
tree: cc7c18d6dd63a9ce946ba46777a4cd0f1ae0a6bb
  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 in one of the communication channels documented at get involved.

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.