-
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
visibility issues after #12337 #12444
Comments
In case it wasn't clear from the initial description, I am trying to get our filters to see core extensions, e.g.:
|
I'll look into this later today. With some workable solution in envoy-filter-example. In general |
Workaround for envoyproxy#12444, while we figure out a permanent solution. Signed-off-by: Raul Gutierrez Segales <[email protected]>
If we can't figure out a solution by EOD, we could merge #12451 to workaround this in the meanwhile. |
Workaround for #12444, while we figure out a permanent solution. Signed-off-by: Raul Gutierrez Segales <[email protected]>
We still need to make the pass through filter public visible, will send a PR shortly. |
Regardless of the fix here we definitely want the pass through filter to be public I'd think (see #12463). |
Workaround for envoyproxy#12444, while we figure out a permanent solution. Signed-off-by: Raul Gutierrez Segales <[email protected]>
Workaround for envoyproxy#12444, while we figure out a permanent solution. Signed-off-by: Raul Gutierrez Segales <[email protected]> Signed-off-by: chaoqinli <[email protected]>
Commit Message: Revert buffer filter visibility back to public Additional Description: After bringing in #12337, we are unable to build the router check tool as we build it with the buffer filter extension, which is no longer visible to the target we use. This change reverts the visibility change for the buffer filter back to public. Risk Level: Low Testing: N/A Docs Changes: N/A Release Notes: N/A Part of #12444 Signed-off-by: Lisa Lu <[email protected]>
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 Signed-off-by: Alyssa Wilk <[email protected]>
After picking up #12337, I can't get our visibility overrides going.
For context, we don't have Envoy as a git submodule and instead it we fetch it via bazel as a tarball using http_archive.
Doing something like:
in our extensions_build_config.bzl fails with:
cc: @lizan @alyssawilk
The text was updated successfully, but these errors were encountered: