amplify-cli icon indicating copy to clipboard operation
amplify-cli copied to clipboard

Cannot deploy AmplifyExportedBackend

Open redjonzaci opened this issue 1 year ago • 5 comments

How did you install the Amplify CLI?

No response

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

No response

Amplify CLI Version

12.12.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.

No manual changes made

Describe the bug

cdk deploy fails with the following error: Error: Parameter with logical ID 'AppSyncApiName' was not found in the template

Expected behavior

should deploy

Reproduction steps

https://docs.amplify.aws/gen1/react/tools/cli/usage/export-to-cdk/

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

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

redjonzaci avatar Jul 30 '24 10:07 redjonzaci

tried the following blog post too and got the same error: https://aws.amazon.com/blogs/mobile/export-amplify-backends-to-cdk-and-use-with-existing-deployment-pipelines/

redjonzaci avatar Jul 30 '24 11:07 redjonzaci

any update?

redjonzaci avatar Aug 07 '24 13:08 redjonzaci

Hey, could you ensure if the amplify-export-manifest.json contains the AppSyncApiName parameter present with a value.

ykethan avatar Aug 16 '24 15:08 ykethan

it does, and i made no manual changes to what is generated by amplify export

redjonzaci avatar Aug 16 '24 17:08 redjonzaci

Hey @redjonzaci, tried reproducing this error with a sample API but could not reproduce this error. If you could share a zip of exported folder on a discord I can try to reproduce the error message and dive into possible mitigation steps.

ykethan avatar Aug 21 '24 16:08 ykethan

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue.

ykethan avatar Oct 21 '24 15:10 ykethan

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.

github-actions[bot] avatar Oct 21 '24 15:10 github-actions[bot]