- update changelog below
- update rockspec version
- update version in
handler.lua
- commit as
chore(*) release x.y.z
- tag commit as
x.y.z
- push commit and tags
- upload to luarocks;
luarocks upload kong-plugin-aws-lambda-x.y.z-1.rockspec --api-key=abc...
- test rockspec;
luarocks install kong-plugin-aws-lambda
- fix: handle multivalueheaders #59
- tests: just fix the test suite so that it works with kong repo too
- fix: respect
skip_large_bodies
config setting when using AWS API Gateway compatibility
- tests: just fix test suite for upcoming change to
ssl_cert
on Kong project
- fix:
skip_large_bodies
to honor config setting
- feat: adding support for 'isBase64Encoded' flag in Lambda function responses
- fix: respect
skip_large_bodies
config setting even when not using AWS API Gateway compatibility
- Change
luaossl
tolua-resty-openssl
- fix: do not validate region name against hardcoded list of regions
- feat: add
host
configuration to allow for custom Lambda endpoints
- Fix: when reusing the proxy based connection do not do the handshake again.
- revamped HTTP connect method that allows for connection reuse in scenarios with a proxy and/or ssl based connections
- Maintenance release for CI purposes
- Encrypt IAM access and secret keys when relevant
- fix: reduce notice-level message to debug, to reduce log noise
- feat: added 3 regions; eu-north-1, me-south-1, eu-west-3
- Remove the no-longer supported
run_on
field from plugin config schema
- Renamed from
liamp
toaws-lambda
to supersede theaws-lambda
plugin from Kong core. - Note that this version number is just to indicate it supersedes the
previously build in one. The effective change from version 2.0 (build in)
of the aws-lambda plugin to 3.0 (this) is the combined set of changes
mentioned below for Liamp versions
0.1.0
and0.2.0
.
- chore: convert the plugin to the PDK and new DB (developed against Kong 1.x)
- feat: if no credentiuals are provided, the plugin will automatically fetch EC2 or ECS credentials and use the AWS IAM roles retrieved for accessing the Lambda.
- feat: new option
awsgateway_compatible
to make the serialized request compatible with the AWS gateway format, making the plugin a drop-in replacement - feat: new option
skip_large_bodies
to enable really large bodies (that have been cached to disk) to also be sent to the Lambda. Use with care! - feat: added the ability to connect to the Lambda through a proxy