sst: `handler and runtime must be set when PackageType is Zip`
diffing urn:pulumi:arpad::nolas::sst:aws:Function$aws:lambda/function:Function::CrmApiFunction:
handler and runtime must be set when PackageType is Zip
We are currently on 0.1.29 due to this error (and the ports one). We have about 8 people on the team working with their local stages. We could get them to do sst remove and then sst dev again but I saw this error happening before on other versions on Discord - so we’d like to upgrade whenever we are sure in some way that future upgrades don’t require removing infra (wouldn’t be that big of a problem if cloudfront wouldn’t take so long to create or delete).
Let me know if I can provide anything extra, I checked the state file but I think it’s the old one not the state it’s trying to deploy, so there wasn’t anything interesting there.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 4
- Comments: 31 (16 by maintainers)
Quick update… we managed to track down the issue.
Working on a fix. Will keep everyone posted.
I need some help tracking this down.
When someone run get this error, can u send the following to my email frank@sst.dev
Pushed out a fix in v3.1.18.
I’m pretty confident this fixes it. If not, let’s reopen this.
Thanks everyone!
@fwang This still happens on
sst diff.sst deployworks fine.SST version: 3.0.70
@fwang that’s right. I don’t have the error anymore because I deleted the entire stack and recreated it. I must also say that I didn’t create the stack with 0.1.40, it was created with a previous version (I don’t know which one anymore) - maybe this is important? My stack is also relatively complicated, I have from 10 to 15 lambdas, a cloudfront distribution, an ECS service, 2 API gateways, login with Cognito … The error was clearly pointing to a specific Lambda but deleting it from the stack was still showing this error, it’s as much as I can say … Sorry I can’t help more on that but if that happens again, I will try to provide more info
I found a possible partial solution but it still involves removing resources:
Be aware that if you have Routers that have a function as dependency, it will delete the router too. But at least you don’t delete databases.