Dynamically route prefix_rewrite

[Bhawna4tech]

How to dynamically route prefix_rewrite

Description:

I want to redirect an incoming request to envoy to one of my services.
For example: I have two services bookings and orders. I want to route to orders/{valueGiven}/sometask when the system gets the request for bookings/{valueGiven}/sometask. I tried doing below solution. It's not working as expected.

                    {
                        "match": {
                          "regex": "/bookings/(.*)/sometask"
                        },
                        "route": {
                          "prefix_rewrite": "/orders/$1/sometask",
                          "cluster": "order_service"
                        }
                      }

When I send request bookings/1234/sometask, system should route to orders/1234/sometask
In the logs I am getting : method=GET path="/orders/$1/sometask", order not found. The expected behavior should get path with the path parameters passed.

[zyfjeff]

@Bhawna4tech the variable is not currently supported, there is no way to use $1 to refer to regular matching to the content

[techygarg]

@zyfjeff: Thanks for prompt response. As we have limited knowledge with Envoy so far, do you see any other feasible way, we can achieve it.

[zyfjeff]

@techygarg #3977 This problem is very similar with you

[Bhawna4tech]

@zyfjeff: Thanks for sharing the link. Yeah, it is same scenario. As no one has responded yet, it looks like it is not feasible currently in envoy, correct ?

[dio]

It seems it is useful to have captured params to be used for subsequent prefix_rewrite-ing.

[BailyTroyer]

Has this been addressed? I am trying to do the same and have found no documentation regarding capture groups in envoy.

[zuercher]

I'm closing this as a duplicate of #2092, which I believe is being worked on.