Supported Events about archive_aws-lambda-go-event HOT 5 OPEN

Integrated missing events and reordered.

For CloudWatch Events, there is something not so clear in the doc. In fact here are a lot of different CloudWatch events, and we should be more specific than the generic documentation and create specific named types for each of them. What do you think?

There are also other events that aren't really documented, but they exist. Examples are those proposed in AWS Lambda test event configuration in the console, like CloudFront or CodePipeline. I think we should gather as much information as possible through the different docs, etc and decide to normalize them and put them here?

from archive_aws-lambda-go-event.

31f5dfb Amazon DynamoDB Streams ✔️

from archive_aws-lambda-go-event.

The list is missing the following:

• AWS CodeCommit
• Amazon Lex
• CloudWatch Events is ambiguous, it shows twice on their list, once with Scheduled and once without

I propose to order it and rename the items to match the list on the AWS side, in order to easily keep track on changes on their side.

from archive_aws-lambda-go-event.

Hi @cristim @fsenart , I'd like to add a Alexa Event and response but not sure where to start. Maybe you can help? 😄 My stuff is in https://github.com/lenfree/alexa-fb-lambda/blob/master/build/decode.go#L5.

from archive_aws-lambda-go-event.

Hi @lenfree,

First of all thx for your interest in this project and your willingness to contribute. Adding a new event is pretty simple:

1. Find the exhaustive set of properties and types involved in your event by crunching the AWS doc, printing incoming raw event in AWS Lambda, etc.
2. Document extensively each field by trying to really understand the purpose of each field via AWS documentation or other sources. The idea is to provide high quality events in order to prevent users the hassle of browsing the web looking for the meaning of each field. I agree that the AWS doc is sometimes very poor regarding this aspect.
3. Follow the conventions used in other provided events such as naming Event, EventRecord, etc, files doc.go, decorder,go, definition.go, etc.
4. Submit a pull request and we will be happy to review and merge your work.

In the meantime, if you need any help, etc please fork the project and I will assist you.

from archive_aws-lambda-go-event.