-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: take two on upstream visibility rules #12692
Conversation
Signed-off-by: Alyssa Wilk <[email protected]>
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 <[email protected]>
# 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems reasonable. I can imagine a finer grained system, but this is fine as a starting point to limit the visibility in Envoy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just name this EXTENSION_PACKAGE_VISIBILITY
?
Signed-off-by: Alyssa Wilk <[email protected]>
Signed-off-by: Alyssa Wilk <[email protected]>
Signed-off-by: Alyssa Wilk <[email protected]>
@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 <[email protected]>
So with:
this works for us. Thanks! [ we do reference a lot of Envoy extensions... the gzip stuff, the crypto stuff, etc. ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for us -- thanks!
@lizan any other thoughts? |
@lizan ping? |
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