hasura/graphql-engine

add more boilerplates for event triggers

Open

#431 opened on Sep 13, 2018

View on GitHub
 (5 comments) (0 reactions) (1 assignee)TypeScript (31,371 stars) (2,787 forks)batch import
a/eventing/data-triggersc/communitye/intermediategood first issuehelp wantedp/high

Description

Need more examples on event triggers for various platform on different languages

  • aws-lambda
    • node 8
    • java
    • csharp
  • google-cloud-functions
    • python
  • azure-functions
    • python
  • zeit-serverless-docker

Contributor guide

Tech stack
javascriptjavacsharppython
Domain
documentationcloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with serverless compute (AWS Lambda, GCP Cloud Functions, Azure Functions)Basic Node.js, Java, C#, PythonUnderstanding of Hasura event triggers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine the existing event trigger examples in the repository (likely under /docs/event triggers/). Note the assignee on the issue—coordinate with them to avoid duplication. Implement each platform language combination following the pattern of existing examples, ensuring correct configuration for Hasura's event trigger system.