spin out and upgrade Lambda plugin

[Tieske]

The plugin now lives in its own repo.

New features (see changelog):

• 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

Note on versioning: the update was developed separately, hence the updates are in the changelog under 0.1.0. After renaming the external plugin to aws-lambda the version was bumped to 3.0.0 to supersede the existing (internal Kong) version at 2.0.0.

[Tieske]

CI fails on a LuaRocks error;

Error: Build error: Failed installing kong/plugins/aws-lambda/v4.lua in /home/travis/install-cache/f99b7d5b0a5f6c9d070ff6ce527637ac/luarocks/lib/luarocks/rocks-5.1/kong/1.3.0-0/lua/kong/plugins/aws-lambda/v4.lua: The source and destination are the same files

[ghost]

Removing these lines from the rockspec:

kong/kong-1.3.0-0.rockspec

Lines 348 to 350 in fe3088a

	["kong.plugins.aws-lambda.handler"] = "kong/plugins/aws-lambda/handler.lua",
	["kong.plugins.aws-lambda.schema"] = "kong/plugins/aws-lambda/schema.lua",
	["kong.plugins.aws-lambda.v4"] = "kong/plugins/aws-lambda/v4.lua",

I'm able to successfully run make dev in my clean Ubuntu machine. I think it makes sense since we're removing it from the codebase.

[Tieske]

@murillopaula good catch! updated

[ghost]

@Tieske rebase current 'next' branch to make travis happy

[Tieske]

rebase current 'next' branch to make travis happy

had already done so, but needed a few job-restarts to finally pass

[ghost]

@Tieske FYI the plugin's CI tests pass when pointing to your 'lambda' branch: Kong/kong-plugin-aws-lambda#7

[kikito]

Hi, I have approved this change on this repo. However, I believe that some work is needed on the new aws-lambda repo. In particular, these:

* 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

Seem to be missing.

[Tieske]

@kikito the changelog was updated (and merged), see Kong/kong-plugin-aws-lambda#9