thrift_proxy: add service name matching to router implementation (#4130)
Currently, the thrift router only supports method matching as a way to route thrift requests. This builds on that by adding the ability to specify a service name that is used when matching. This change updates the RouteMatch proto definition to use a oneof field to indicate what type of matching should be done, as well as an invert flag that will allow for inverse matching rules. Additionally: * ensure new RouteEntryImplBase implementations check that inversion and wildcard matching are not enabled at the same time, as this would result in no matches for a route * implement service matching as checking the prefix of the method name, as that's how it's implemented in thrift *Risk Level:* Low *Testing:* * new and existing unit tests pass. * updated integration test use new matching rules and ensure that expected upstreams receive requests. *Documentation:* n/a *Release Notes:* n/a Signed-off-by: Brian Ramos <brirams@users.noreply.github.com> Mirrored from https://github.com/envoyproxy/envoy @ 27fb1d353bb13d778a7fb70186e77ad7ce1080e1pull/620/head
parent
77d13eacf7
commit
34928fe3ad
1 changed files with 17 additions and 4 deletions
Loading…
Reference in new issue