Currently, Wasm extension requires a proto for the module configuration: https://github.com/envoyproxy/envoy/blob/master/api/envoy/extensions/wasm/v3/wasm.proto#L40

It is not clear how to use this Any field. The host generally does not have the protobuf schema for the module configuration (it's not compiled in). So all the envoy tooling dealing with protos is not effective.

Additionally, it creates an expectation that the module uses protos for its configuration. This is problematic since a minimal Wasm module with protobuf in it is over 1MB in size.

The request is to change it back to bytes. The module should decide whether to use protobuf or just JSON.

cc @jplevyak @lizan