Skip to content

Latest commit

 

History

History
14 lines (8 loc) · 1.43 KB

File metadata and controls

14 lines (8 loc) · 1.43 KB

Aggregation, flattening and pagination example

The main goal of this configuration is to merge and flatten data from two different services and paginate the results.

Endpoints

  1. /list/{page}
    This endpoint takes a page number as a parameter and serves paginated results of the merged data from the internal /__internal-endpoint-list endpoint. The output encoding is set to no-op, which means that the response is not encoded or transformed.

    The modifier/lua-proxy extra config is used to run a Lua script (merge-and-paginate.lua) that takes care of merging the data and paginating it. The live option is set to true, which allows the Lua script to be updated at runtime without restarting the service.

    The response body of the endpoint is the result of the merge_users_and_paginate(req, resp) function from the Lua script.

  2. /__internal-endpoint-list
    This internal endpoint retrieves data from two services, /agents.json and /users.json, and merges the results using the modifier/jmespath extra config. The expr field contains the JMESPath expression used to merge the data into a single users_list array.

    The plugin/req-resp-modifier extra config is used to apply an IP filter, named ip-filter. The filter is configured to deny all IP addresses except 127.0.0.1, which means that only local requests can access this internal endpoint.

You can run this example by executing a docker-compose up