[roll] Roll fuchsia [power][broker] Handle ElementControl in ElementSchema

Updates AddElement implementation to use a client-provided
ElementControl channel when provided via ElementSchema. In this case,
the returned server-provided ElementControl channel is closed by the
server.

For temporary backwards compatibility, AddElement still returns a valid
and open ElementControl channel if the client doesn't provide one. This
behavior will be removed once all clients have migrated to pass their
own ElementControl channels.

Original-Bug: b/346997964
Test: New integration test for the new client-provided channel behavior.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1069217
Original-Revision: b9b9f1ca9b4ace699ba32d5cd6f332186497b235
GitOrigin-RevId: 16963e0648fe1608c4f82d0c9eb039b9adc59421
Change-Id: I9ddd5ea6eab9a659449de07ecf9f522f8d20dc78
1 file changed
tree: 0e5b77752101f1f53aad8d0ebef5097dc6cae2f7
  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.