build: take two on upstream visibility rules#12692
build: take two on upstream visibility rules#12692alyssawilk merged 6 commits intoenvoyproxy:masterfrom
Conversation
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
|
I just merged envoyproxy/envoy-filter-example#128, can we bump filter-example SHA in CI to see if it works? |
|
pass-through filter is manually tagged public (not using the default rules) so I think it's orthogonal from this change. More interesting would be if it were private, and envoy filter example had an override to explicitly depend on it, but I agree that one should be public (and possibly moved to core but organization tbd) |
|
@alyssawilk it is manually tagged public after the previous take. There were a couple PRs. |
|
Right, but this PR doesn't revert that being public, so I guess I'm not sure what bumping proves? |
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
| # These can be changed to ["//visibility:public"], for downstream builds which | ||
| # need to directly reference Envoy extensions. | ||
| EXTENSION_CONFIG_VISIBILITY = ["//:extension_config"] | ||
| EXTENSION_EXTENSION_PACKAGE_VISIBILITY = ["//:extension_library"] |
There was a problem hiding this comment.
This seems reasonable. I can imagine a finer grained system, but this is fine as a starting point to limit the visibility in Envoy.
lizan
left a comment
There was a problem hiding this comment.
Thanks this looks good. just one nit
| # These can be changed to ["//visibility:public"], for downstream builds which | ||
| # need to directly reference Envoy extensions. | ||
| EXTENSION_CONFIG_VISIBILITY = ["//:extension_config"] | ||
| EXTENSION_EXTENSION_PACKAGE_VISIBILITY = ["//:extension_library"] |
There was a problem hiding this comment.
Just name this EXTENSION_PACKAGE_VISIBILITY?
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
|
@rgs1 can you test this PR with your BUILD? |
|
/wait-any |
Hey sorry for the late response I was OOO; yes I can give this a try. Mind merging master first tho? |
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
|
So with: this works for us. Thanks! [ we do reference a lot of Envoy extensions... the gzip stuff, the crypto stuff, etc. ] |
|
@lizan any other thoughts? |
|
@lizan ping? |
|
cc @yanavlasov @auni53 |
Setting things up so downstream folks can just override with visibility:public but upstream avoids core code depending on extensions.
Risk Level: medium (of breaking builds, instructions of how to unbreak included)
Testing: manually swapped to public, all works.
Docs Changes: included
Release Notes: overkill
Fixes #12444