aws-amplify / aws-amplify/amplify-cli
No error output even no zip file in var directory
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
### If applicable, what version of Node.js are you using?
v16.18.0
### Amplify CLI Version
10.7.3
### What operating system are you using?
MAC M1
### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes
### Describe the bug
Backendbuild fails locally and remote
Errormessage not usable
No zip log File generated
### Expected behavior
Should show me a error message or at least generate an error zip
### Reproduction steps
amplify migrate perhaps my GraphQL.shema is wrong but how can I find out ?
### Project Identifier
36d4c405c5d2a8293fe6a5b2a72ea07f
### Log output
```
2023-02-26T20:59:19.583Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]rack-[***]is-[***]933"}])
2023-02-26T20:59:20.127Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]ral-[***]28:stack/[***]ify-[***]rack-[***]is-[***]933/[***]b380-[***]55-[***]ed-[***]13-[***]68700"}])
2023-02-26T20:59:49.578Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]rack-[***]is-[***]933"}])
2023-02-26T20:59:50.143Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]ral-[***]28:stack/[***]ify-[***]rack-[***]is-[***]933/[***]b380-[***]55-[***]ed-[***]13-[***]68700"}])
2023-02-26T20:59:52.094Z|error : Resource is not in the state stackUpdateComplete
DeploymentFault: Resource is not in the state stackUpdateComplete
2023-02-26T21:06:15.068Z|info : amplify version core {"version":true,"yes":false}
```
### Additional information
Here the srcreenOutput
I made an amplify serve. At the end You can see that there is no error zip even no directory with the zip
? Are you sure you want to continue? Yes
Deployment failed.
Deploying root stack Artbarrack [ =========================-----------
amplify-artbarrack-alis-235933 AWS::CloudFormation::Stack UPDATE_
storageItemStorage AWS::CloudFormation::Stack UPDATE_
functionartbarrackf557cb0ePre… AWS::CloudFormation::Stack UPDATE_
authartbarrackf557cb0e AWS::CloudFormation::Stack UPDATE_
apiartApi AWS::CloudFormation::Stack UPDATE_
authuserPoolGroups AWS::CloudFormation::Stack UPDATE_
Deployed auth artbarrackf557cb0e [ ===================================
Deployed auth userPoolGroups [ =======================================
Deploying function myqueryresolver [ ---------------------------------
Deploying function reorganize [ --------------------------------------
Deployed function artbarrackf557cb0ePreAuthentication [ ==============
🛑 The following resources failed to deploy:
🛑 Resource is not in the state stackUpdateComplete
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: bd709ceb-87fc-4626-b1f9-4bc6e378104a
✅ Report saved: /var/folders/2w/cs5c31ln07l07km7mt594pnc0000gq/T/Artbarrack/report-1677445189855.zip
✔ Done
Project Identifier: 36d4c405c5d2a8293fe6a5b2a72ea07f
daphne code$ cd /var/folders/2w/cs5c31ln07l07km7mt594pnc0000gq/T/A
Pressing TAB now to see the possibilities:
AppTranslocation/ AudioComponentRegistrar/
No Artbarrack subDir as mentioned in the Report saved line.
### 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.
Contributor guide
Research direction
Start with the amplify serve or amplify migrate deployment flow and the log output showing the report path under /var/folders. Check how the CLI reports deployment failures and writes the referenced zip, then verify the user-visible error and report location against the filesystem. Done means the failure has a usable error message and the reported archive is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, graphql, typescript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100