workflow

Description

The workflow plugin is used to introduce lua-resty-expr to provide complex traffic control features.

Attributes

NameTypeRequiredDefaultValid valuesDescription
rules.casearray[array]TrueList of variables to match for filtering requests for conditional traffic split. It is in the format {variable operator value}. For example, {“arg_name”, “==”, “json”}. The variables here are consistent with NGINX internal variables. For details on supported operators, you can refer to lua-resty-expr.
rules.actionsarray[object]TrueThe action to be performed when the case matches successfully. Currently, only one element is supported in actions. The first child element of the actions’ only element can be return or limit-count.

actions Attributes

return

NameTypeRequiredDefaultValid valuesDescription
actions[1].returnstringFalseReturn directly to the client.
actions[1].[2].codeintegerFalseHTTP status code returned to the client.

limit-count

NameTypeRequiredDefaultValid valuesDescription
actions[1].limit-countstringFalseExecute the functions of the limit-count plugin.
actions[1].[2]objectFalseConfiguration of limit-count plugin, group is not supported.
workflow - 图1note

In rules, match case in order according to the index of the rules, and execute actions directly if case match.

Enabling the Plugin

You can configure the workflow plugin on a Route as shown below:

  1. curl http://127.0.0.1:9180/apisix/admin/routes/1 \
  2. -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
  3. {
  4.     "uri":"/hello/*",
  5.     "plugins":{
  6.         "workflow":{
  7.             "rules":[
  8.                 {
  9.                     "case":[
  10.                         ["uri", "==", "/hello/rejected"]
  11.                     ],
  12.                     "actions":[
  13.                         [
  14.                             "return",
  15.                             {"code": 403}
  16.                         ]
  17.                     ]
  18.                 },
  19.                 {
  20.                     "case":[
  21.                         ["uri", "==", "/hello/v2/appid"]
  22.                     ],
  23.                     "actions":[
  24.                         [
  25.                             "limit-count",
  26.                             {
  27.                                 "count":2,
  28.                                 "time_window":60,
  29.                                 "rejected_code":429
  30.                             }
  31.                         ]
  32.                     ]
  33.                 }
  34.             ]
  35.         }
  36.     },
  37.     "upstream":{
  38.         "type":"roundrobin",
  39.         "nodes":{
  40.             "127.0.0.1:1980":1
  41.         }
  42.     }
  43. }'

Here, the workflow Plugin is enabled on the Route. If the request matches the case in the rules, the actions will be executed.

Example 1: If the requested uri is /hello/rejected, the status code 403 is returned to the client

  1. curl http://127.0.0.1:9080/hello/rejected -i
  2. HTTP/1.1 403 Forbidden
  3. ......
  5. {"error_msg":"rejected by workflow"}

Example 2: if the request uri is /hello/v2/appid, the workflow plugin would execute the limit-count plugin

  1. curl http://127.0.0.1:0080/hello/v2/appid -i
  2. HTTP/1.1 200 OK
  1. curl http://127.0.0.1:0080/hello/v2/appid -i
  2. HTTP/1.1 200 OK
  1. curl http://127.0.0.1:0080/hello/v2/appid -i
  2. HTTP/1.1 429 Too Many Requests

Example 3: if the request can not match any case in the rules, the workflow plugin would do nothing

  1. curl http://127.0.0.1:0080/hello/fake -i
  2. HTTP/1.1 200 OK

Disable Plugin

To disable the workflow plugin, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect.

  1. curl http://127.0.0.1:9180/apisix/admin/routes/1 \
  2. -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
  3. {
  4.     "uri":"/hello/*",
  5.     "upstream": {
  6.         "type": "roundrobin",
  7.         "nodes": {
  8.             "127.0.0.1:1980": 1
  9.         }
  10.     }
  11. }'