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

Get amplify/#current-cloud-backend/amplify-meta.json' does not exist from init and pull #13633

Closed
2 tasks done
yusukegoto opened this issue Mar 6, 2024 · 3 comments
Closed
2 tasks done
Labels
pending-triage Issue is pending triage platform-pull Issues related to `amplify pull`

Comments

@yusukegoto
Copy link

How did you install the Amplify CLI?

asdf

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

v20.10.0

Amplify CLI Version

12.10.0

What operating system are you using?

macOS 14.3.1

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

No.

Describe the bug

I'm getting amplify/#current-cloud-backend/amplify-meta.json' does not exist error from amplify init and amplify pull.
And there is a nested #current-cloud-backend

$ ls amplify/\#current-cloud-backend/\#current-cloud-backend    
amplify-meta.json       awscloudformation       function                tsconfig.json
api                     backend-config.json     package.json
auth                    cli.json

Expected behavior

amplify init and amplify pull run successfully.

Reproduction steps

amplify init --envName myenv --appId MY_ID--debug
amplify pull --envName myenv --appId MY_ID --debug

Project Identifier

Project Identifier: eeac7938f8313a01fd2c8550bffa6759

report-1709716696135.zip

Log output

2024-03-06T09:10:20.811Z|info : amplify init core  {"envName":"[***]stiv","appId":"[***]zavzyf","debug":true,"yes":false}
2024-03-06T09:10:20.859Z|info : @aws-amplify/amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2024-03-06T09:10:27.599Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["phoenix-sandbox-tmp"])
2024-03-06T09:10:27.601Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1","output":"json"}])
2024-03-06T09:10:27.601Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["phoenix-sandbox-tmp"])
2024-03-06T09:10:28.338Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["phoenix-sandbox-tmp"])
2024-03-06T09:10:28.341Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1","output":"json"}])
2024-03-06T09:10:28.342Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["phoenix-sandbox-tmp"])
2024-03-06T09:10:28.350Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2024-03-06T09:10:28.354Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]xcore-[***]stiv-[***]646-[***]ment"}])
2024-03-06T09:10:36.146Z|info : amplify-provider-awscloudformation.initialize-env.run.cfn.updateamplifyMetaFileWithStackOutputs([{"StackName":"[***]ify-[***]xcore-[***]stiv-[***]646"}])
2024-03-06T09:10:36.151Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["phoenix-sandbox-tmp"])
2024-03-06T09:10:36.152Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1","output":"json"}])
2024-03-06T09:10:36.153Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["phoenix-sandbox-tmp"])
2024-03-06T09:10:36.165Z|info : amplify-provider-awscloudformation.aws-cfn.updateamplifyMetaFileWithStackOutputs.cfn.listStackResources([{"StackName":"[***]ify-[***]xcore-[***]stiv-[***]646"}])
2024-03-06T09:10:36.951Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]ify-[***]xcore-[***]stiv-[***]646"}])
2024-03-06T09:10:37.519Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]mLambdaStack-[***]62OEX7/[***]fc90-[***]c0-[***]ee-[***]d9-[***]57331"}])
2024-03-06T09:10:37.524Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]coreapi-[***]SBROI/[***]ca10-[***]c0-[***]ee-[***]4b-[***]cf687"}])
2024-03-06T09:10:37.526Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]reresource-[***]KMSZ9/[***]5fd0-[***]bf-[***]ee-[***]03-[***]8766d"}])
2024-03-06T09:10:37.528Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]olGroups-[***]SJB6X/[***]6900-[***]c0-[***]ee-[***]d7-[***]bce5f"}])
2024-03-06T09:10:37.531Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]UsersToGroup-[***]1RDIEE/[***]1610-[***]c0-[***]ee-[***]0b-[***]5f65d"}])
2024-03-06T09:10:37.534Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]ToCoreAdmin-[***]DUZPN/[***]7f90-[***]c0-[***]ee-[***]b2-[***]3982b"}])
2024-03-06T09:10:37.538Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]ognitoUser-[***]YIIH03/[***]5ed0-[***]c0-[***]ee-[***]21-[***]cdc45"}])
2024-03-06T09:10:37.543Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]oUserAndGroup-[***]LQ9ESN/[***]77d0-[***]c0-[***]ee-[***]21-[***]cdc45"}])
2024-03-06T09:10:37.549Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]eCommonLayer-[***]I8069/[***]efb0-[***]bf-[***]ee-[***]6f-[***]a9507"}])
2024-03-06T09:10:37.556Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]st-[***]72:stack/[***]ify-[***]xcore-[***]stiv-[***]646-[***]cePostConfirmation-[***]R1UJW1/[***]5580-[***]c0-[***]ee-[***]a8-[***]4cfa7"}])
2024-03-06T09:10:40.388Z|error : Could not initialize platform for 'sbtestiv': File at path: '/Users/yusukegoto/src/immo/hey/phoenix-core/amplify/#current-cloud-backend/amplify-meta.json' does not exist
ProjectInitFault: Could not initialize platform for 'sbtestiv': File at path: '/Users/yusukegoto/src/immo/hey/phoenix-core/amplify/#current-cloud-backend/amplify-meta.json' does not exist

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.
@yusukegoto yusukegoto added the pending-triage Issue is pending triage label Mar 6, 2024
@ykethan
Copy link
Member

ykethan commented Mar 6, 2024

Hey @yusukegoto, thank you for reaching out. Could you download the #current-cloud-backend.zip from the S3 deployment bucket on the AWS console. The bucket name should end with deployment and contain the app name.
if you do observe a nested current-cloud-backend in the zip, we could try carefully re-zipping the contents without creating a nested folder similar to as follows, then upload the zip and try pulling the env in a new empty folder outside your existing project directory to test.

cd /#current-cloud-backend/
zip -r "../#current-cloud-backend.zip" *

@ykethan ykethan added pending-response Issue is pending response from the issue author platform-pull Issues related to `amplify pull` labels Mar 6, 2024
@yusukegoto
Copy link
Author

I've resolved this issue in a different way. I moved all files under a child #current-cloud-backend onto a parent #current-cloud-backend and running amplify push --force worked 🤷‍♂️
Then I can't try your suggested way. I'll try next if I have this again.

Thanks @ykethan !
I'm closing this issue

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Mar 11, 2024
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage Issue is pending triage platform-pull Issues related to `amplify pull`
Projects
None yet
Development

No branches or pull requests

2 participants