The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development. This plugin provides functionality for the API category, allowing for the creation and management of GraphQL and REST based backends for your amplify project.
Describe the bug
this is a follow-on to aws-amplify/amplify-cli#3693. when i try to add a new REST API (using amplify add api > REST) that accesses a DynamoDB that created using the @model directive in creating an AppSync GraphQL, the DB is not visible in the "Select the category" step in setting up the new REST API. I'm using the "Hello world" function template.
Amplify CLI Version
4.23.0
To Reproduce
1-amplify add api, choose GraphQL, create some @models.
2-amplify add api, choose REST, and use Hello world as function template. the @model-created DynamoDB will not be listed as a category.
Expected behavior
The user should see a list of DynamoDB tables, including those created using @model directive.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Linux Mint
Node Version: 13.14.0
Additional context
I know that the table that i'm trying to access was successfully created, because i can see it in AWS console, and can read/write to it.
Only DynamoDB tables created using the amplify storage category is checked in the current implementation.
I will mark this as an enhancement and discuss with the team.
Describe the bug this is a follow-on to aws-amplify/amplify-cli#3693. when i try to add a new REST API (using
amplify add api
>REST
) that accesses a DynamoDB that created using the @model directive in creating an AppSync GraphQL, the DB is not visible in the "Select the category" step in setting up the new REST API. I'm using the "Hello world" function template.Amplify CLI Version 4.23.0
To Reproduce 1-
amplify add api
, choose GraphQL, create some@model
s. 2-amplify add api
, choose REST, and useHello world
as function template. the @model-created DynamoDB will not be listed as a category.Expected behavior The user should see a list of DynamoDB tables, including those created using @model directive.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context I know that the table that i'm trying to access was successfully created, because i can see it in AWS console, and can read/write to it.