Skip to content
This repository has been archived by the owner on Aug 27, 2021. It is now read-only.

fix(docs) Update changelog to clarify the changes from aws-lambda 2 to 3 #9

Merged
merged 1 commit into from
Oct 8, 2019
Merged

fix(docs) Update changelog to clarify the changes from aws-lambda 2 to 3 #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,17 @@
## 3.0.0
## aws-lambda 3.0.0

- supersede the `aws-lambda` plugin from Kong core
- Renamed from `liamp` to `aws-lambda` to supersede the `aws-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` and `0.2.0`.

## 0.2.0
## Liamp 0.2.0

- chore: convert the plugin to the PDK and new DB (developed against Kong 1.x)

## 0.1.0
## Liamp 0.1.0

- 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
Expand Down