[roll] Roll fuchsia [bazel] Rm usages of bazel_input_resource[_directory]

These templates are deprecated and will be removed soon.

NOTE: bazel_input_resource is still used by
export_fuchsia_package_to_bazel.gni, which will need a separate change
to migrate with a build fence since I'm seeing incremental build
failures related to duplicate manifests defined for the same package.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1105653
Original-Revision: 62ca2136deeb9a0c4623724b4707e97e8fca0eed
GitOrigin-RevId: 657caca2891ad99a5a8ea9196a121fdd157c9c66
Change-Id: Icb998b66b92a2bd5ee056b9a7c1a538ee84f6d57
1 file changed
tree: c3a829ddb3c700ee008df6502ded3b67e2b8a37c
  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.