-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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.
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
aws-appsync: Support DataSource type NONE #7144
Comments
This makes sense. Do you have any examples we could see of this in use? Just want to understand the use-case a little better. |
A simple use case for a NONE data source is any query that returns static data that is purely defined in VTL. The use case described in the description above is about a way to send events from the server to the client without actually needing to invoke Lambda or DynamoDB. The schema defines a mutation and a subscription that uses See also: |
awesome, I ran into those docs but your explanation helps. Checking out the PR. |
fixed in #7145 |
Currently aws-appsync only supports data source types
AMAZON_DYNAMODB
andAWS_LAMBDA
. This is a request to add support for typeNONE
.Use Case
To trigger GraphQL subscriptions from the backend, it's common to create a mutation that is triggerd by the backend. These don't necessarily need an actual datasource, and the AppSync data source type
NONE
can be used instead.Proposed Solution
Add a new type
NoneDataSource
and a methodGraphQLApi.addNoneDataSource()
.Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: