Open donovano opened 4 years ago
Hey @donovano, this is definitely something we’re interested in supporting. In particular, it’s a really viable approach for solving #41 in App Mesh.
For HTTP filter support, do you have any filters in mind that you would want to write or use? Would love to hear some more about what sort of functionality you’re looking for in the filter in general.
An example would be to apply a custom policy, inspecting header values for compliance, inserting a custom header for processing by the receiving service/proxy etc.
Any update on this?
Tell us about your request Envoy WASM support is already deployed in Istio and is planned to be generally available in Envoy 1.14 or 1.15 at this stage. Do you intend to make this available in Appmesh once it has matured in the mainstream Envoy? This will avoid having enable users to supply their own build on Envoy if they wanted to because users would be able to add HTTP filters dynamically to the Envoy you manage that supports WASM.
Which integration(s) is this request for? Proxy
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? WIth the current Envoy, if the Appmesh user wanted to write a custom HTTP filter they'd have to have the ability to supply their own build of Envoy. This is hard and not ideal. With the new Envoy WASM model, the Appmesh user can supply a custom HTTP filter without having to supply a custom Envoy binary that contains the filter.
Are you currently working around this issue? No
Additional context None
Attachments None