Release 3.16

[tkan145]

How to generate policy file

Build apicast image

make runtime-image IMAGE_NAME=apicast-runtime-image:release-3.16

Run apicast

$ cat <<EOF >config.json
{
   "services": [
      {
         "proxy": {
             "hosts": ["one"],
             "proxy_rules": [],
             "api_backend": "https://echo-api.3scale.net",
             "policy_chain": []
         }
      }
   ]
}
EOF

$ docker run -ti -p 8090:8090 --name apicast --rm -v $PWD/config.json:/opt/app/config.json:ro --env THREESCALE_CONFIG_FILE=/opt/app/config.json --env APICAST_LOG_LEVEL=debug --env APICAST_CONFIGURATION_LOADER=lazy --env APICAST_CONFIGURATION_CACHE=0 --env THREESCALE_DEPLOYMENT_ENV=staging --env BACKEND_ENDPOINT_OVERRIDE=http://127.0.0.1:3000 --env APICAST_WORKERS=1 apicast-runtime-image:release-3.16

Fetch policies

$ mkdir -p doc/policies_list/3.16.0
$ curl -v -H "Host: one" http://127.0.0.1:8090/policies -o policies.latest.json
# pretty print and fix string encoding issues
$ jq --sort-keys . policies.latest.json > doc/policies_list/3.16.0/policies.json

[lcavalle]

Suggested change

	- Concat filtered services into a single log [THREESCALE-10894](https://issues.redhat.com/browse/THREESCALE-10894) [PR #1493](https://github.com/3scale/APIcast/pull/1493)
	- Concatenated filtered services into a single log [THREESCALE-10894](https://issues.redhat.com/browse/THREESCALE-10894) [PR #1493](https://github.com/3scale/APIcast/pull/1493)

[lcavalle]

Suggested change

	- Add `enable_extended_context` to allow JWT Claim Check access full request context [PR #1535](https://github.com/3scale/APIcast/pull/1535) [THREESCALE-9510](https://issues.redhat.com/browse/THREESCALE-9510)
	- Added `enable_extended_context` to allow JWT Claim Check access full request context [PR #1535](https://github.com/3scale/APIcast/pull/1535) [THREESCALE-9510](https://issues.redhat.com/browse/THREESCALE-9510)

[lcavalle]

Suggested change

	- Use luarocks v3 [PR #1513](https://github.com/3scale/APIcast/pull/1513)
	- Used luarocks v3 [PR #1513](https://github.com/3scale/APIcast/pull/1513)

[lcavalle]

Suggested change

	- Remove opentracing support [PR #1520](https://github.com/3scale/APIcast/pull/1520) [THREESCALE-11603](https://issues.redhat.com/browse/THREESCALE-11603)
	- Removed OpenTracing support [PR #1520](https://github.com/3scale/APIcast/pull/1520) [THREESCALE-11603](https://issues.redhat.com/browse/THREESCALE-11603)

[lcavalle]

Added some minor reviews to fix typos.

[eguzki]

LGTM

minor: the verification steps have 3.15 instead of 3.16, but not a big deal.

Ready to be merged when requested changes are addressed

[tkan145]

@eguzki thanks, the verification steps have been updated to 3.16

@lcavalle thanks for your feedback, could you please give it another review?

[tkan145]

It seems there is an issue with luarocks luarocks/luarocks#1797 causing our CI pipeline to fail.

@eguzki should we wait for the fix?

[eguzki]

It seems there is an issue with luarocks luarocks/luarocks#1797 causing our CI pipeline to fail.

@eguzki should we wait for the fix?

Being a PR to set release data, I would merge without waiting for tests. Make sure images are being built and pushed to quay.io

[tkan145]

On luarocks install <package name> luarocks will load the manifest and look for the package, however luajit can only hold 65536 items in a table and the numbers of rocks has surpass this number since May 29, hence the following error

When user call luarocks install <package name> , luarocks will load the manifest and search for the package, however luajit can only hold 65536 entries in a table and the number of rocks has exceeded this number since May 29, hence the following error

main function has more than 65536 constants

The solution seems to be:

1. Install the rocks directly and bypass manifest lookup.

luarocks install --deps-mode=none --tree /usr/local https://luarocks.org/manifests/pintsized/lua-resty-http-0.17.1-0.src.rock

2. Use older version of manifest. See Upgrade luarocks to v3.12.0 #1552
3. Overwrite the rocks_server to use older manifest via luarocks config file.
4. Switch to use json manifest feat: allow loading json manifest luarocks/luarocks#1798

Both option (1) and (2) won't work for dev-image due to we also need use rover to install rocks.
Option (3) works but seem evasive
Option (4) we will need to wait for a new release of luarocks and perhaps another fix for https://github.com/luarocks/luarocks-site

Since we are still able to build runtime image (due to bypass manifest lookup and install the rocks directly). I will merge this PR