APINestedStack Error about serverless-plugin-split-stacks HOT 9 CLOSED

Do you have a lot of separate functions/endpoints? An alternative is to combine them together, and just have one, or maybe a few.

functions:
  api:
    handler: api.js
    events:
      - http ANY /
      - http ANY /{any+}

or per some kind of logical thing

functions:
  fooApi:
    handler: api.js
    events:
      - http ANY /foo
      - http ANY /foo/{any+}
  barApi:
    handler: api.js
    events:
      - http ANY /bar
      - http ANY /bar/{any+}

But not "getFoo", "putFoo", "postFoo", etc.

You can see my module https://github.com/dougmoscrop/serverless-http which will let you use routing like Koa/Express to make the function handler code dead simple

from serverless-plugin-split-stacks.

Yeah, this is another CloudFormation limit that this plugin does not have logic for trying to solve. It's basically a case of having to further divide in to even more nested stacks because of output/input limit, not just resource count. I can imagine how we might accomplish it, just not done.

from serverless-plugin-split-stacks.

oops i was really hoping to have a solution... Is there any other alternatives left or should i architect my endpoints in a way that it doesn't affect resource count or size limit ?

from serverless-plugin-split-stacks.

The problem is it is a existing application, so i cannot change as your suggestion now. Also all the request validations are handled in API Gateway request validator. I have also requested for limit increase with AWS support. Let me see how it goes

from serverless-plugin-split-stacks.

Even combining events does not work :(

Any update on this?

from serverless-plugin-split-stacks.

The easiest way for me to help is if you can share with me the actual CF templates so I don't have to guess about what is being exposed and make a focused suggestion/fix. Obviously you should anonymize/sanitize anything in your examples.

from serverless-plugin-split-stacks.

Now it's working, but I think that combine resource is just a patch. If you have a lot of endpoints the problem will appear again :/

from serverless-plugin-split-stacks.

You're right, unfortunately this plugin will not by you an endless ramp, you still have to try to split up concerns in to separate services.

One way to help 'move the cliff', so to speak, would be to modify the sub-stack splitting logic located here to do something like:

if (Object.keys(stack.Resources).length < 200 && Object.keys(stack.Outputs).length < 60) {
}

this would move some API resources to a new stack (APINestedStack2) but I am not sure if there would be other issues there. It's a game of cat and mouse.

from serverless-plugin-split-stacks.

Sorry, this is a duplicate of #15

I will move my comment to there.

from serverless-plugin-split-stacks.