graphql
graphql copied to clipboard
serverless-components
⚡ Deploy and manage GraphQL applications on serverless infrastructure easily, cheaply and scale massively.
graphql 3.0.3 I have graphql components configured to deploy to different stages each with a different provider defined in the serverless web ui with each provider being a different aws...
I've inherited a codebase using this component, and am getting the error below when attempting to deploy. Obviously the error is remote, but I can't see why I would be...
AppSync now has full support for completely custom auth via Lambda authorizers (https://aws.amazon.com/blogs/mobile/appsync-lambda-auth/)
When an appsync api is deployed and then extended with additional graphql components that reference it's `appId` the resolvers they attached are disconnected. To fix each component that references the...
In order for this Serverless component to be usable for anything more than a hobbyist project, it should support schema stitching out of the box. As GraphQL projects and codebases...
It's common practice to write initialization process like db connection (opening db connection and reuse it in handler function) at the top of handler function and write finalization process like...
Unexpected errors can occur when resolvers.js is loaded as part of the deploy process. For example, it's common to create things like DB connections outside of the handler so that...
Hi, I need to implement real-time notifications, and the recommended way of doing it with app sync seems to be local resolvers: See here: https://docs.aws.amazon.com/appsync/latest/devguide/tutorial-local-resolvers.html How can I get this...
It seems that the name of the instance as specified in the serverless.yml is also used as the name withing app sync, plus some unique id. It would be preferable...
The graphql-starter needs that to prevent accidentally uploading keys.
Metadata
Owner
Metadata
⚡ Deploy and manage GraphQL applications on serverless infrastructure easily, cheaply and scale massively.