Skip to content
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

MappingTemplate error on all resolvers after deleting a DynamoDB table #2507

Closed
2 tasks done
manjumallesh1 opened this issue Apr 26, 2024 · 3 comments
Closed
2 tasks done
Labels
question Further information is requested transferred

Comments

@manjumallesh1
Copy link

manjumallesh1 commented Apr 26, 2024

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v16.16.0

Amplify CLI Version

12.11.1

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Deleted a DynamoDB table and added back with the same name

Describe the bug

After successful deletion of a DynamodDB table via GraphQL schema changes and amplify pull, there is no data returned by the resolvers

query MyQuery {
  getTesting(id: "ce9e1e7d-fb33-4e94-9eb8-c7c3d9da26a3") {
    id
  }
}

provides the following results

{
  "data": {
    "getTesting": null
  },
  "errors": [
    {
      "path": [
        "getTesting"
      ],
      "data": null,
      "errorType": "MappingTemplate",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "Value for field '$[operation]' not found."
    }
  ]
}

Expected behavior

The query should return the response

Reproduction steps

  1. Manually deleted a DynamoDB table greated via GraphQL schema
  2. Added the table back with the same name
  3. Now, deleted the table via the GraphQL schema changes

Project Identifier

edc573327dd31dc69d57250ee36b5cfb

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@ykethan
Copy link
Member

ykethan commented Apr 26, 2024

Hey👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

@ykethan ykethan transferred this issue from aws-amplify/amplify-cli Apr 26, 2024
@phani-srikar phani-srikar added question Further information is requested and removed pending-triage labels Apr 28, 2024
@phani-srikar
Copy link
Contributor

Closing this in favor of the issue with the similar setup and error message #2503

Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested transferred
Projects
None yet
Development

No branches or pull requests

3 participants