Lukas Siemon

We are now using [yaml-boost](https://github.com/simlu/yaml-boost) and it works really well. Basically it replaces `serverless.yml` with `serverless.core.yml` and creates a new `serverless.js` that loads the rename yml file and parses is...

@iDVB Yes, we are still using `yaml-boost` in a lot of projects (it has become our bread and butter). I will take a look at the ticket you opened in...

So the accepted solution here requires you to take down the routes. Not really acceptable if you are just changing marginal things (e.g. making path parameter required) and the route...

@laurensV We stopped using path parameter entirely and route and validate in application logic with a single resolver route (using lambda-serverless-api on npm, disclaimer I'm the author). There are still...

@HyperBrain Thank you very much for that (rather long) post. There some great points in there (and some that I didn't fully understand). So let's dig into it: `The configuration...

@thomasmichaelwallace I knew we were not the only ones trying to resolve this problem. Similar to how you describe it we tried to nicely separate our configuration, but serverless has...

@thomasmichaelwallace Very good discussion here! I'm just going to take a step back and list some observations: - yml is the recommended standard by serverless that most people will use...

@thomasmichaelwallace If you are just using plain yaml without file inclusion this is easy. However if you use the extended serverless yml functionality it is actually more complex to switch...

FYI: We have a similar problem trying to use `@vercel/ncc` for deploying this in our serverless application.

Just ran into this as well. Weird bug and hard to understand why it's happening.