traffic-split plugin update

[MekelCon]

Version info: APISIX 3.0.0

I try to use route, grouped inside a service using the Admin API.

I created the service A with a plugin config 1:
{ "plugins" : { "pluginX" : { // plugin config 1 } } .... }

Then i PUT my route Foo with service_id A as reference :
{ "service_id" : "A" .... }

Later when I update the Service A with a new config plugin config 2:
{ "plugins" : { "pluginX" : { // plugin config 2 } } .... }

I expected the new plugin configuration to be up to date when calling again the route Foo but i appear it is not the case, the config 1 still apply.
I have to PUT again one of my sub route to make it up to date with latest service plugin config.
Is it a normal behavior ? Am i doing or expecting something wrong ?

Thank you for your help.

[tzssangglass]

{ "plugins" : { "pluginX" : { // plugin config 1 } } .... }

{ "service_id" : "A" .... }

{ "plugins" : { "pluginX" : { // plugin config 2 } } .... }

Can you give details of the configuration?

[MekelCon]

Hello thank you for you reply !
While trying to reproduce a simple case to give you an example, i discovered that it works as expected in most cases.
So the issue seems to be related to my specific case.

What i want to achieve :
I have a consumer allowed to use a version v1 of an api.
I want to move him to use the v2 of the same api.
To achieve this is use the traffc-split plugin with will send the right host header to the backend based on the consumer_name

Here is what i do :
Step 1
Create a consumer with the key-auth plugin

PUT .../admin/consumers
//  with body
{
    "username": "service_update_case",
    "plugins": {
        "key-auth": {
            "key": "epic-key"
        }
    }
}

Step 2
Create my Service :

PUT /admin/services/service-update-case
// Body
{
    "plugins": {
        "key-auth": {
            "header": "X-SERVICE-UPDATE-CASE"
        },
        "traffic-split": {
            "rules": [
                {
                    "match": [
                        {
                            "vars": [
                                [
                                    "consumer_name",
                                    "in",
                                    ["conusmer-X", "service_update_case"]
                                ]
                            ]
                        }
                    ],
                    "weighted_upstreams": [
                        {
                            "upstream": {
                                "type": "roundrobin",
                                "upstream_host": "my-api.v1",
                                "pass_host": "rewrite",
                                "nodes": {
                                    "1.2.3.4:443": 1
                                }
                            }
                        }
                    ]
                },
                {
                    "match": [
                        {
                            "vars": [
                                [
                                    "consumer_name",
                                    "in",
                                    ["consumer-Y"]
                                ]
                            ]
                        }
                    ],
                    "weighted_upstreams": [
                        {
                            "upstream": {
                                "type": "roundrobin",
                                "upstream_host": "my-api.v2",
                                "pass_host": "rewrite",
                                "nodes": {
                                    "1.2.3.4:443": 1
                                }
                            }
                        }
                    ]
                }
            ]
        }
    },
    "desc": "api multi version"
}

Step 3
Create a route inside the service :

PUT ...admin/routes/service-update-case
{
    "methods": [
        "GET"
    ],
    "uri": "/service-update-case/get",
    "service_id": "service-update-case"
}

With this config :

• consumer-X, service_update_case consumers will be redirected to v1 of my backend.
• consumer-Y will be redirected to v2 of my backend
  And it work as expected ! Until i want update my service with the following :

PUT /admin/services/service-update-case
// Body
{
    "plugins": {
        "key-auth": {
            "header": "X-SERVICE-UPDATE-CASE"
        },
        "traffic-split": {
            "rules": [
                {
                    "match": [
                        {
                            "vars": [
                                [
                                    "consumer_name",
                                    "in",
                                    ["conusmer-X"]
                                ]
                            ]
                        }
                    ],
                    "weighted_upstreams": [
                        {
                            "upstream": {
                                "type": "roundrobin",
                                "upstream_host": "my-api.v1",
                                "pass_host": "rewrite",
                                "nodes": {
                                    "1.2.3.4:443": 1
                                }
                            }
                        }
                    ]
                },
                {
                    "match": [
                        {
                            "vars": [
                                [
                                    "consumer_name",
                                    "in",
                                    ["consumer-Y", "service_update_case"]
                                ]
                            ]
                        }
                    ],
                    "weighted_upstreams": [
                        {
                            "upstream": {
                                "type": "roundrobin",
                                "upstream_host": "my-api.v2",
                                "pass_host": "rewrite",
                                "nodes": {
                                    "1.2.3.4:443": 1
                                }
                            }
                        }
                    ]
                }
            ]
        }
    },
    "desc": "api multi version"
}

It is same request as Step 2 excepted that service_update_case move from the v1 list to the v2 list in the traffic-split.rules.match attribute.
And here, when i do a call to consume /service-update-case/get as service_update_case consumer i am still redirected to the v1.

Later if i do a PUT on the route previously created, same request Step 3 :

PUT ...admin/routes/service-update-case
{
    "methods": [
        "GET"
    ],
    "uri": "/service-update-case/get",
    "service_id": "service-update-case"
}

I am then well redirected to the v2.

Thank you for taking the time to read this 😄
Hope it's clear.

[tzssangglass]

Very clearly, I have reproduced it. A very interesting bug that I'm analyzing.

[MekelCon]

For information fixed by #8481