Route match with dynamic_metadata

[Luciano Callero]

Hi, envoy-users.

I've been trying and failing to match and route a request based on information added to the dynamic_metadata space after the request is successfully authenticated by an external auth-server, which is configured with gRPC.

I managed to debug the service_metadata space with Lua, I can print the info in the logs, but the service_metadata matcher apparently cannot access the information.

The related docs: https://www.envoyproxy.io/docs/envoy/v1.22.0/api-v3/type/matcher/v3/metadata.proto#envoy-v3-api-msg-type-matcher-v3-metadatamatcher

I've put a comment with the config details in the issue https://github.com/envoyproxy/envoy/issues/19910, which seems to be the same problem.

I appreciate any insights you could give.

[Luciano Callero]

Related comment in the issue:
https://github.com/envoyproxy/envoy/issues/19910#issuecomment-1084333169