You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so way back when I fixed the default visibility rules so extensions were in general not visible to core code and non-extension tests.
That said, it relies on maintainers remembering to not let folks fix visibility rules, as individual contributors don't know it's problematic (e.g. #20560 (comment)) and that's clearly not a good plan.
I think as a follow up to #9953 we should have CI out disallow "visibility" in //extension BUILD files, to require admin approval of any violations of the extension policy. cc @envoyproxy/envoy-maintainers for any other ideas / objections and cc @phlax for if you can pick it up or if you want to suffer reviewing my awful python :-P
The text was updated successfully, but these errors were encountered:
Testing: ran against envoyproxy#20552 :-)
Leaving those BUILD files in as example exemptions.
Fixesenvoyproxy#20589
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
so way back when I fixed the default visibility rules so extensions were in general not visible to core code and non-extension tests.
That said, it relies on maintainers remembering to not let folks fix visibility rules, as individual contributors don't know it's problematic (e.g. #20560 (comment)) and that's clearly not a good plan.
I think as a follow up to #9953 we should have CI out disallow "visibility" in //extension BUILD files, to require admin approval of any violations of the extension policy. cc @envoyproxy/envoy-maintainers for any other ideas / objections and cc @phlax for if you can pick it up or if you want to suffer reviewing my awful python :-P
The text was updated successfully, but these errors were encountered: