You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Echo filter is now only Network filter. Refactor would be required to enable echo support in HTTP filters.
Echo filter is quite useful for testing complex envoy configurations. Having ability to enable echo per specific matching criteria would be beneficial.
Creating issue to validate idea - I would like to contribute the change.
My first thought is that if we were to introduce an HTTP echo filter it should be a separate filter. There's already generic code to implement envoy::type::matcher::v3::MetadataMatcher so I don't think there's going to be a lot of duplication between network and http echo filters that support metadata matching.
I think the first step would be to propose the API changes for the existing echo filter and the new http echo filter and go from there.
cc @htuch@alyssawilk since they nominally own the echo network filter
Title: Extending Echo filter to match specific metadata
Description:
Extending Echo filter to support metadataMatcher.
Echo filter is now only Network filter. Refactor would be required to enable echo support in HTTP filters.
Echo filter is quite useful for testing complex envoy configurations. Having ability to enable echo per specific matching criteria would be beneficial.
Creating issue to validate idea - I would like to contribute the change.
Relevant Links
https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/echo/v3/echo.proto
The text was updated successfully, but these errors were encountered: