data-plane-api(CircleCI)
73f41bf9e0
TapDS API ( #7287 )
...
Signed-off-by: Yuval Kohavi <yuval.kohavi@gmail.com>
Mirrored from https://github.com/envoyproxy/envoy @ 154d7a0fc31d279a07f10f33ccdabb136ea25413
6 years ago
data-plane-api(CircleCI)
de2a8387e0
fix bazel query ( #5886 )
...
fix bazel query
Risk Level: Low
Testing: built //source/exe:envoy-static
Signed-off-by: Dan Rosen <mergeconflict@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ d841d20b101584786d4d44190a78da313768b146
6 years ago
data-plane-api(CircleCI)
7ed25fb1d4
api: fix wrong java_package option in a proto file ( #5853 )
...
Signed-off-by: Penn (Dapeng) Zhang <zdapeng@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 8ddd3b7ceefc5116c80457528b9c876f172e3ff1
6 years ago
data-plane-api(CircleCI)
86c352428b
api: add java proto options to avoid risk of future breakage ( #5764 )
...
As discussed with @snowp in [envoyproxy/java-control-plane#87 (comment)](https://github.com/envoyproxy/java-control-plane/issues/87#issuecomment-456537248 ) and [envoyproxy/java-control-plane#87 (comment)](https://github.com/envoyproxy/java-control-plane/issues/87#issuecomment-457649859 ), adding these options will avoid the risk of having API breaking changes on the generated java code as the proto files evolve.
Risk Level_: Medium
Note that e.g. [envoyproxy/java-control-plane](https://github.com/envoyproxy/java-control-plane ) will have to do a refactoring when they sync the proto files next time.
Signed-off-by: Penn (Dapeng) Zhang <zdapeng@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 4a5f85809cef13be47873483789a5a7bb64ded7c
6 years ago
data-plane-api(CircleCI)
1df7f3ad16
tap transport: refactor to use common tap framework ( #5724 )
...
This commit refactors the tap transport socket to use the common
tap extension configuration and tap matching infrastructure. More
match conditions will be added in a future PR as well as additional
cleanups that have been marked with TODOs.
One result of this PR is that the HTTP tap filter can now have a static
configuration as well as write to a file per tap sink.
All future tap PRs should be smaller and more targeted after this one.
Signed-off-by: Matt Klein <mklein@lyft.com>
Mirrored from https://github.com/envoyproxy/envoy @ f37ebdc14f4c0adf0e90aabddae833355c0cec1b
6 years ago