[roll] Roll fuchsia [ffx][config] Can detect config domains in isolate

This makes it so that when you set up an isolated environment context,
if you give it a current working directory it will attempt to find a
configuration domain from that path as in the detect logic.

The reasoning for this is that generally, in the situations where we
currently advise using config domains, you still want project-specific
config to be available even if you don't want user config and other
similar stuff breaking in.

Currently, out of tree scripts that use isolation are passing in the
hidden `--env-root` argument to achieve this effect, and it doesn't make
sense to have them do so all the time.

Original-Fixed: b/290946797
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/959571
Original-Revision: 2cc4d25233e28fe01b3ccd35d30443d3ec66a963
GitOrigin-RevId: 5b43763102ebdec248a39dcdfbdf5f8cc15ff391
Change-Id: I8b850e61edf207cd8e08bbe7699a8b760a15ccc3
1 file changed
tree: 4b8a659dd4c1f518483fcce3890ebae620429400
  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.