-
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
Eliminate/prevent dependencies on extensions from core #9953
Comments
+1 yes please. If you are going to fix this can you also potentially fix #6736? It's related in the sense that by default we build and link all extensions into some of the server integration tests. Optimally the core integration tests should depend on only a build with a very limited set of extensions. |
I think @yanavlasov is working on this. Also discussing fixing #6736 as well. |
Risk Level: medium (of build breakage) Testing: n/a Docs Changes: n/a Release Notes: n/a Part of #9953 Signed-off-by: Alyssa Wilk <[email protected]>
…proxy#12337) Risk Level: medium (of build breakage) Testing: n/a Docs Changes: n/a Release Notes: n/a Part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]>
…proxy#12337) Risk Level: medium (of build breakage) Testing: n/a Docs Changes: n/a Release Notes: n/a Part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]> Signed-off-by: chaoqinli <[email protected]>
Tests for core extension (TLS) depending on non-core extension with new cert verifier functionality -> broken build if you only want the transport_sockets TLS extension. |
part of #9953 Signed-off-by: Alyssa Wilk <[email protected]>
Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: inline part of #9953 Signed-off-by: Alyssa Wilk <[email protected]>
Part of #9953 Signed-off-by: Alyssa Wilk <[email protected]>
part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]> Signed-off-by: Josh Perry <[email protected]>
Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: inline part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]> Signed-off-by: Josh Perry <[email protected]>
Part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]> Signed-off-by: Josh Perry <[email protected]>
I think @alyssawilk has been picking away at this. @alyssawilk are we done with this or is there more to do? |
Down from ~30 to ~6 but not compelte source/extensions/filters/network/common/BUILD: # Used by core. TODO(#9953) clean up. |
… it (#20571) Part of #9953 Signed-off-by: Alyssa Wilk <[email protected]>
Risk Level: n/a (visibility only) part of #9953 Signed-off-by: Alyssa Wilk <[email protected]>
Part of #9953 Signed-off-by: Alyssa Wilk <[email protected]>
Fixes #9953 Signed-off-by: Alyssa Wilk <[email protected]>
DONE. |
… it (envoyproxy#20571) Part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]>
Risk Level: n/a (visibility only) part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]>
…proxy#20588) Part of envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]>
Fixes envoyproxy#9953 Signed-off-by: Alyssa Wilk <[email protected]>
There are some cases where core Envoy code (or tests) depends on extensions. One example:
are used by:
This poses an issue for users like Google, who import only specific whitelisted extensions. We have to disable tests that depend on non-whitelisted extensions. I think we'd like to add some logic to check_format or similar, to catch these dependencies before they're introduced.
Not sure if this is related to #7903, likely seems related to #2910.
The text was updated successfully, but these errors were encountered: