tree f30b8332c89c5aafdb8c01350dda06b4783af512
parent b6d1345a5398a45ae90ba9769ca63789b300ce40
author stuartmorgan <stuartmorgan@google.com> 1626989204 -0700
committer GitHub <noreply@github.com> 1626989204 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg+eKUCRBK7hj4Ov3rIwAAKG0IACMoNMrUrwWUATJnfbohxKTg
 5v9GbhRWzhP7gjKjsp3KBPdW1AdlU+4JPGgU/MvyojUkVP7bQsI1Qw29Iw9mskgJ
 YnRwoKOMqlQroNOrltk5EkWb92B5A1daKir0zMvljDgF0s6tP0fyVOpbdxpZr1zq
 81/mBAzkkKNLwYeimfMg5I/e7xwwbtzSdWsEv+1IFTRZVxPrqSpxDEw+xKpkG9Rz
 E8c62FqMRvMCdOMr912EKvXXxCuD+i0DscmtAbpeamMh3Pxw25/XFD44fXzrGf30
 CH+pbxpVZmDflcp8BhDWm0/t/FH6IoI0fzhbRR1g375TYL8UlgM92Qwiu1tZeI4=
 =02Z9
 -----END PGP SIGNATURE-----
 

[flutter_plugin_tools] Support YAML exception lists (#4183)

Currently the tool accepts `--custom-analysis` to allow a list of packages for which custom `analysis_options.yaml` are allowed, and `--exclude` to exclude a set of packages when running a command against all, or all changed, packages. This results in these exception lists being embedded into CI configuration files (e.g., .cirrus.yaml) or scripts, which makes them harder to maintain, and harder to re-use in other contexts (local runs, new CI systems).

This adds support for both flags to accept paths to YAML files that contain the lists, so that they can be maintained separately, and with inline comments about the reasons things are on the lists.

Also updates the CI to use this new support, eliminating those lists from `.cirrus.yaml` and `tool_runner.sh`

Fixes https://github.com/flutter/flutter/issues/86799