-
Notifications
You must be signed in to change notification settings - Fork 819
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
Can't access DynamoDB tables created by GraphQL API on a new lambda function #3693
Comments
I will mark this as an enhancement. |
I'm using amplify version 4.16.1 and this works for me. |
@iShavgula Are you sure? can you share a screenshot of a lambda function creation with access to DynamoDB tables created by AppSync? |
@iShavgula That's amazing, I didn't know it was in the storage category. This helps a lot, I was doing it manually until now. Weird how @UnleashedMind marked this as an enhancement if it already exists |
@iShavgula I tried doing this all along, guess I needed to create a |
@idanlo it has not been long time since it’s available, maybe couple of days. |
i would also like to see this functionality described by @idanlo. i have an IoT device that can only write a REST API (i.e., POST), but i want to be able to read that data on a mobile device using AppSync/GraphQL. so two different APIs (GQL and REST) need to be able to talk to the same DynamoDB. i created the DB using "amplify create api" > "graphql ", and now need to create a REST API that points to that @model-created DB. |
@davidhgray look at the comments above, there is an image showing how to do that |
@idanlo for some reason, at the "select the category" step, when i select "storage", no DBs are shown to me. it's as if the CLI is just skipping this step. |
@davidhgray maybe you should create a new issue, this one is already buried in the list and no one will see it if I re open |
From the image you have not selected "storage" category. Need to press space to select when the item is highlighted.
|
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
Whenever creating a new lambda function using
amplify add function
or adding a REST API usingamplify add api
and choosing REST, the CLI asks for a function template to use, and when I chooseCRUD function for Amazon DynamoDB table (Integration with Amazon API Gateway and Amazon DynamoDB)
and I try to use existing DynamoDB tables, it says there aren't any tables. I guess you could use #2463 in order to make it work for creating lambda functions for accessing tables, and not just triggers for tables.To Reproduce
amplify add api
, chooseGraphQL
, create some@model
s, thenamplify add api
, chooseREST
, and useCRUD function for Amazon DynamoDB table (Integration with Amazon API Gateway and Amazon DynamoDB)
as template, selectDynamoDB table configured in the current Amplify project
and you get an error.Expected behavior
The user should be able to see a list of all tables, also tables created using the
@model
directive on the GraphQL schemaThe text was updated successfully, but these errors were encountered: