-
Notifications
You must be signed in to change notification settings - Fork 115
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
Generating a CloudWatch log, not deleted in "sls remove". #57
Comments
I'm also having issues with redeployment. Getting the following error:
I had to manually delete that log group on CloudWatch. |
@cdichiara @alvarodms What version were you using, |
It should have been the options bug from Warmup log group is created and removed properly. (edit) |
Oh, thanks, I just updated - I was way back at 3.3.0, that's probably it. |
I am experiencing this problem with 3.6.2-rc.1 any advise ? |
Any reason to not update to the latest version 4.4.3-rc.1? |
Bump. |
Hi @antoniuslin, quick googling shows me that this is a known problem of Serverless when using multiple stages (serverless/serverless#5057) |
Hi @juanjoDiaz, I can confirm that multiple stages of deployment. My issue seems to have disappeared (resolved?) when specifying the service & stage in the lambda warmer config block itself as you hinted from the link. E.g.
It resulted in a unique lambda log group per stage for the service. |
That's odd since that should be the default name anyway. |
Honestly, I don't remember and I'd just sooner chalk it up to my not RTFM & hasty copypasta from some article about this nice & nifty plugin somewhere. If I had just spent a couple of proper minutes reading the
|
Hi, nice plugin. :)
I believe you're generating a CloudWatch log "--warmup", but it's not registered with the CloudFormation stack, so when you uninstall the deployment it persists and interferes with redeployment, I think.
The text was updated successfully, but these errors were encountered: