Getting "Too Many Requests"
Hello,
I have a lot of models (50+) and I'm getting the error "Too Many Requests" when the deploy is about to finish. I'm only deploying about 5 lambdas, but as stated earlier there are a large number of models.
As a follow up on the discussion in serverless/serverless#85 I wanted to open this issue here to know your comments. The issue in question starts with the comment https://github.com/serverless/serverless/issues/885#issuecomment-291581397.
In serverless/serverless#85 it is mentioned that this might be caused by a plugin, and since this is the only plugin I'm using in this project, I thought that it would be cool to know your thoughts about this :)
Thanks in advance!
[Container] 2017/04/06 13:26:07 Stack Outputs
.... some output here about what has been deployed...
[Container] 2017/04/06 13:26:08
[Container] 2017/04/06 13:26:08
Too Many Requests Exception ----------------------------
[Container] 2017/04/06 13:26:08
[Container] 2017/04/06 13:26:08 Too Many Requests
[Container] 2017/04/06 13:26:08
[Container] 2017/04/06 13:26:08 For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
[Container] 2017/04/06 13:26:08
[Container] 2017/04/06 13:26:08 Get Support --------------------------------------------
[Container] 2017/04/06 13:26:08 Docs: docs.serverless.com
[Container] 2017/04/06 13:26:08 Bugs: github.com/serverless/serverless/issues
[Container] 2017/04/06 13:26:08 Chat: gitter.im/serverless
[Container] 2017/04/06 13:26:08 Chat: gitter.im/serverless/serverless
[Container] 2017/04/06 13:26:08
[Container] 2017/04/06 13:26:08 Your Environment Information -----------------------------
[Container] 2017/04/06 13:26:08 OS: linux
[Container] 2017/04/06 13:26:08 Serverless Version: 1.10.2
[Container] 2017/04/06 13:26:08 Serverless Version: 1.10.2
Cloudformation now supports documentation parts, so using the SDK is no longer needed. I will update this soon, so rate limiting is no problem any more. This should also increase speed.
Is this resolved? Still seeing this error in v1.1.0.
Unfortunately, this is not resolved. There is a roadblock for this because of the limit of CloudFormation resources that will explode with this change.