Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add more boilerplates for event triggers #431

Open
9 tasks
shahidhk opened this issue Sep 13, 2018 · 5 comments
Open
9 tasks

add more boilerplates for event triggers #431

shahidhk opened this issue Sep 13, 2018 · 5 comments
Assignees
@tirumaraiselvan
Labels
a/eventing/data-triggers c/community Related to community content e/intermediate can be wrapped up in a week good first issue Good for newcomers help wanted Good candidate for contribution. Community help wanted! p/high candidate for being included in the upcoming sprint

Comments

@shahidhk
Copy link
Member

shahidhk commented Sep 13, 2018 •
edited by shark-h
Loading

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
@shahidhk shahidhk added help wanted Good candidate for contribution. Community help wanted! good first issue Good for newcomers c/community Related to community content labels Sep 13, 2018
@jamesgeorge007
Copy link
Contributor

@shahidhk Could you elaborate further?

@shahidhk
Copy link
Member Author

shahidhk commented Oct 8, 2018 •
edited by shark-h
Loading

@jamesgeorge007 We need more examples to be added to community/boilerplates/event-triggers

hexmind added a commit to hexmind/graphql-engine that referenced this issue Oct 14, 2018
@hexmind
hasura#431 add more boilerplates for serverless triggers
5d69c2d 
Added serverless-triggers/AWS lambda/Java/echo
hexmind added a commit to hexmind/graphql-engine that referenced this issue Oct 14, 2018
@hexmind
hasura#431 add more boilerplates for serverless triggers
c101752 
Added serverless-triggers/AWS lambda/Java/echo
@hexmind hexmind mentioned this issue Oct 14, 2018
Merged
21 tasks
@nathanwaters
Copy link
Contributor

+1 cloudflare workers. I've emailed their team the repo link

@ganny26 ganny26 mentioned this issue Oct 16, 2018
Merged
21 tasks
@shark-h shark-h changed the title add more boilerplates for serverless triggers add more boilerplates for event triggers Jan 24, 2019
This was referenced Feb 28, 2019
Closed
Closed
Closed
@marionschleifer marionschleifer self-assigned this Jul 10, 2019
@marionschleifer marionschleifer added p/high candidate for being included in the upcoming sprint e/intermediate can be wrapped up in a week labels Jul 10, 2019
@marionschleifer marionschleifer removed their assignment Jul 17, 2019
shahidhk pushed a commit that referenced this issue Aug 23, 2019
@hexmind @shahidhk
add more boilerplates for serverless triggers (#748)
669bb40 
#431
@LiTO773 LiTO773 mentioned this issue Oct 2, 2019
Merged
@LiTO773
Copy link
Contributor

LiTO773 commented Oct 2, 2019

Hi 🖐, I've added an echo template for Netlify Functions.

polRk pushed a commit to polRk/graphql-engine that referenced this issue Feb 12, 2020
@hexmind @polRk
add more boilerplates for serverless triggers (hasura#748)
cbc5a5c 
hasura#431
@abhijeet007rocks8 abhijeet007rocks8 mentioned this issue Oct 19, 2022
Open
21 tasks
@zpg6
Copy link

zpg6 commented Dec 14, 2022

+1 cloudflare workers. I've emailed their team the repo link

+1

@ptakpatryk ptakpatryk mentioned this issue Dec 19, 2023
Open
hasura-bot pushed a commit that referenced this issue Apr 2, 2024
@i-am-tom @hasura-bot
Run cargo fmt in CI (#431)
ec62ea4 
<!-- Thank you for submitting this PR! :) -->

## Description

When I run `cargo fmt` on my branches, it makes more diff than I want.
This PR fixes that by adding `just format` / `just fmt`, and adding it
to a CI job.

<!--
  Questions to consider answering:
  1. What user-facing changes are being made?
2. What are issues related to this PR? (Consider adding `(close
#<issue-no>)` to the PR title)
  3. What is the conceptual design behind this PR?
  4. How can this PR be tested/verified?
  5. Does the PR have limitations?
  6. Does the PR introduce breaking changes?
-->

## Changelog

- Add a changelog entry (in the "Changelog entry" section below) if the
changes in this PR have any user-facing impact. See [changelog
guide](https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide).
- If no changelog is required ignore/remove this section and add a
`no-changelog-required` label to the PR.

### Product
_(Select all products this will be available in)_
- [ ] community-edition
- [ ] cloud
<!-- product : end : DO NOT REMOVE -->

### Type
<!-- See changelog structure:
https://github.com/hasura/graphql-engine-mono/wiki/Changelog-Guide#structure-of-our-changelog
-->
_(Select only one. In case of multiple, choose the most appropriate)_
- [ ] highlight
- [ ] enhancement
- [ ] bugfix
- [ ] behaviour-change
- [ ] performance-enhancement
- [ ] security-fix
<!-- type : end : DO NOT REMOVE -->

### Changelog entry
<!--
  - Add a user understandable changelog entry
- Include all details needed to understand the change. Try including
links to docs or issues if relevant
  - For Highlights start with a H4 heading (#### <entry title>)
  - Get the changelog entry reviewed by your team
-->

_Replace with changelog entry_

<!-- changelog-entry : end : DO NOT REMOVE -->

<!-- changelog : end : DO NOT REMOVE -->

V3_GIT_ORIGIN_REV_ID: e31e352f27b9ad0129c3759fead051b1a8d86758
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tirumaraiselvan tirumaraiselvan

Labels
a/eventing/data-triggers c/community Related to community content e/intermediate can be wrapped up in a week good first issue Good for newcomers help wanted Good candidate for contribution. Community help wanted! p/high candidate for being included in the upcoming sprint
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@nathanwaters @shahidhk @manasag @marionschleifer @tirumaraiselvan @LiTO773 @zpg6 @jamesgeorge007 @shark-h @Stefmore02