search

sst / ion

SST v3
https://sst.dev
MIT License
1.75k stars 214 forks source link

CLI eating deploy errors #949

Open jayair opened 3 weeks ago

jayair commented 3 weeks ago

Some deploy errors are not being shown, running sst deploy --stage prod

SST 3.0.74  ready!

➜  App:        sst-sharp
   Stage:      prod

~  Deploy

✓  Complete

But it wasn't deployed correctly because the output is missing. Happens on sst dev too.

Running it with --print-logs shows the error.

time=2024-08-28T14:05:21.869-04:00 level=ERROR msg="stack run failed" error="failed to run update: exit status 255\ncode: 255\nstdout: Updating (prod):\n\n    pulumi:pulumi:Stack sst-sharp-prod running \n@ updating....\n    sst:aws:Function MyFunction  \n    sst:sst:LinkRef MyFunctionLinkRef  \n    pulumi:pulumi:Stack sst-sharp-prod running error: Running program '/Users/jayair/Desktop/Sandbox/sst-sharp/.sst/platform/sst.config.1724868318555.mjs' failed with an unhandled exception:\n@ updating....\n    aws:cloudwatch:LogGroup MyFunctionLogGroup  \n    aws:iam:Role MyFunctionRole  \n    pulumi:pulumi:Stack sst-sharp-prod **failed** 1 error\n    sst:sst:LinkRef MyFunctionLinkRef  \nDiagnostics:\n  pulumi:pulumi:Stack (sst-sharp-prod):\n    error: Running program '/Users/jayair/Desktop/Sandbox/sst-sharp/.sst/platform/sst.config.1724868318555.mjs' failed with an unhandled exception:\n    \x1b[36m<ref *1>\x1b[39m Error: failed to register new resource MyLayer [aws:lambda/layerVersion:LayerVersion]: 2 UNKNOWN: failed to compute archive hash for \"code\": open /Users/jayair/Desktop/Sandbox/sst-sharp/.sst/platform/sharp-layer.zip: no such file or directory\n        at Object.registerResource \x1b[90m(/Users/jayair/Desktop/Sandbox/sst-sharp/\x1b[39m.sst/platform/node_modules/\x1b[4m@pulumi\x1b[24m/aws/node_modules/\x1b[4m@pulumi\x1b[24m/runtime/resource.ts:455:27\x1b[90m)\x1b[39m\n        at new Resource \x1b[90m(/Users/jayair/Desktop/Sandbox/sst-sharp/\x1b[39m.sst/platform/node_modules/\x1b[4m@pulumi\x1b[24m/aws/node_modules/\x1b[4m@pulumi\x1b[24m/resource.ts:507:13\x1b[90m)\x1b[39m\n        at new CustomResource \x1b[90m(/Users/jayair/Desktop/Sandbox/sst-sharp/\x1b[39m.sst/platform/node_modules/\x1b[4m@pulumi\x1b[24m/aws/node_modules/\x1b[4m@pulumi\x1b[24m/resource.ts:962:9\x1b[90m)\x1b[39m\n        at new LayerVersion \x1b[90m(/Users/jayair/Desktop/Sandbox/sst-sharp/\x1b[39m.sst/platform/node_modules/\x1b[4m@pulumi\x1b[24m/lambda/layerVersion.ts:211:9\x1b[90m)\x1b[39m\n        at run \x1b[90m(file:///Users/jayair/Desktop/Sandbox/sst-sharp/\x1b[39msst.config.ts:14:19\x1b[90m)\x1b[39m\n        at run \x1b[90m(file:///Users/jayair/Desktop/Sandbox/sst-sharp/\x1b[39m.sst/platform/src/auto/run.ts:33:26\x1b[90m)\x1b[39m\n        at \x1b[90mfile:///Users/jayair/Desktop/Sandbox/sst-sharp/\x1b[39meval.ts:4:28\n    \x1b[90m    at ModuleJob.run (node:internal/modules/esm/module_job:218:25)\x1b[39m\n    \x1b[90m    at ModuleLoader.import (node:internal/modules/esm/loader:329:24)\x1b[39m\n    \x1b[90m    at importModuleDynamicallyWrapper (node:internal/vm/module:431:15)\x1b[39m {\n      promise: Promise { \x1b[36m<rejected>\x1b[39m \x1b[36m[Circular *1]\x1b[39m }\n    }\n\nResources:\n    5 unchanged\n\nDuration: 3s\n\n\nstderr: \n"
time=2024-08-28T14:05:21.869-04:00 level=INFO msg="INFO putting summary app=sst-sharp stage=prod"
time=2024-08-28T14:05:21.869-04:00 level=INFO msg="INFO putting data key=summary app=sst-sharp stage=prod/cjslf0i6fopz9i67b4fh5nnc"
time=2024-08-28T14:05:21.994-04:00 level=INFO msg="parsing state"
time=2024-08-28T14:05:22.222-04:00 level=INFO msg="INFO putting links app=sst-sharp stage=prod"
time=2024-08-28T14:05:22.222-04:00 level=INFO msg=publishing type=*project.CompleteEvent
time=2024-08-28T14:05:22.222-04:00 level=INFO msg="done parsing state"
✓  Complete

time=2024-08-28T14:05:22.222-04:00 level=INFO msg="INFO pushing state app=sst-sharp stage=prod from=/Users/jayair/Desktop/Sandbox/sst-sharp/.sst/.pulumi/stacks/sst-sharp/prod.json"
time=2024-08-28T14:05:22.378-04:00 level=INFO msg="INFO unlocking app=sst-sharp stage=prod"
time=2024-08-28T14:05:22.472-04:00 level=INFO msg="shutting down server"
time=2024-08-28T14:05:22.473-04:00 level=INFO msg="server done"
time=2024-08-28T14:05:22.473-04:00 level=ERROR msg="exited with error" err="stack run had errors"
gardner commented 4 days ago

Consider enabling --print-logs when the environment variable CI=true is set.