[roll] Roll fuchsia [routing] Remove mapper from Aggregates

The mapper is cloned to be placed in the aggregate classes.
This means the mapper can't actually be used by scrunity
because the routes are being added to a new mapper.

Remove the mappers from these classes so we can remove
Clone from the Mapper class.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/934912
Original-Revision: e447921ad2c8448ffd3482c197d085c68fd12535
GitOrigin-RevId: b23223ca7ed8e57de317d995969fa4e8cc599378
Change-Id: I58a860494e143a99d2089f4a97bfb676153322ca
1 file changed
tree: 63a2219645c3f25fff9eba2e606bf8d6c66296cd
  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.