-
Notifications
You must be signed in to change notification settings - Fork 73
Still getting Error: The CloudFormation template is invalid: Template format error: Number of resources, 536, is greater than maximum allowed, 500 #159
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
Comments
Same Problem here - it seems the Serverless: [serverless-plugin-split-stacks]: - (root): xxx has a maximum of 500. |
For me, I was only able to get it to work when creating a new service. If you have an existing service, you need to |
You can try commented out the resource you want to move, first, and then uncommenting them after one deploy run. |
We are facing that issue right now, blocked from deploying and moving away from the plugin since we don't find an evident solution |
You should use a custom stacks-map to move resources around. This plugin is very cautious upfront about what resources are safe to move. But I implore you, split your services up, if your stack ever gets in to a bad state you will have a terrible time. "byType" does not move everything, it just does 'of the resources I trust I can move, arrange them by type' You might use https://github.com/dougmoscrop/serverless-plugin-bootstrap to create an entirely separate stack for your persist resources (tables, queues, buckets) |
I am trying to use the serverless split stack, and it is not working. I tried to use a custom stacks map, but it still puts over 500 resources in the root. Can you explain what you mean about "split your services up"? This is my yaml file:
|
I have added the following to in serverless.yml file still i am seeing no changes am i missing anything?
custom:
splitStacks:
perFunction: false
perType: true
perGroupFunction: false
The text was updated successfully, but these errors were encountered: