search

lifadev / archive_aws-lambda-go-event

Type definitions for AWS Lambda event sources.
https://github.com/eawsy/aws-lambda-go-event
Apache License 2.0
77 stars 18 forks source link

Supported Events #1

Open fsenart opened 8 years ago

fsenart commented 8 years ago

This issue tracks the integration of all AWS Lambda supported events. Feel free to open an issue for any unchecked event that doesn't already have one, but please try to keep discussions in a single issue if possible.

Extensive documentation is mandatory for each event.

To report a bug with a completed feature, please open a new issue for the bug.

lion3ls commented 7 years ago

31f5dfb Amazon DynamoDB Streams :heavy_check_mark:

cristim commented 7 years ago

The list is missing the following:

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.

fsenart commented 7 years ago

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?

lenfree commented 7 years ago

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.

fsenart commented 7 years ago

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.