Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Can't access DynamoDB tables created by GraphQL API on a new lambda function
See original GitHub issueDescribe the bug
Whenever creating a new lambda function using amplify add function or adding a REST API using amplify add api and choosing REST, the CLI asks for a function template to use, and when I choose CRUD 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, choose GraphQL, create some @models, then amplify add api, choose REST, and use CRUD function for Amazon DynamoDB table (Integration with Amazon API Gateway and Amazon DynamoDB) as template, select DynamoDB 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 schema
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:13 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@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