graphql-engine/community/boilerplates/event-triggers/aws-lambda
Anon Ray a21f6cd648 introduce v1/graphql (fix #1368) (#2064)
Changes compared to `/v1alpha1/graphql`

* Changed all graphql responses in **/v1/graphql** endpoint to be 200. All graphql clients expect responses to be HTTP 200. Non-200 responses are considered transport layer errors. 

* Errors in http and websocket layer are now consistent and have similar structure.
2019-05-10 11:35:10 +05:30
..
go refactor community content and folder structure (#1353) 2019-01-17 15:57:28 +05:30
nodejs6 introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
nodejs8 introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
python introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
README.md refactor community content and folder structure (#1353) 2019-01-17 15:57:28 +05:30

Boilerplates for AWS Lambda serverless functions and Hasura GraphQL Engine's Event Triggers

Sample cloud functions that can be triggered on changes in the database using GraphQL Engine's Event Triggers.

These are organized in language-specific folders.

NOTE Some of the language/platforms are work in progress. We welcome contributions for the WIP langauages. See issues and the following checklist:

Folder name Use-case Node.js(6) Python Java Go C#
echo echo the trigger payload
mutation insert related data on an insert event using graphql mutation
push-notification send push notification on database event
etl transform the trigger payload and update an algolia index

Pre-requisites

  1. AWS account with billing enabled
  2. Hasura GraphQL Engine