Severi Haverila

i think this still is a really valid feature request. For example in our use case we have a monorepo with multiple frontends and serverless apis that we wish to...

Since (most likely) today retrying the job has not worked for us anymore. When we retry the deployment with serverless it succeeds according to serverless, but might stay in a...

We currently have ~13 sls stacks using the same api gateway (gateway is created in a deployment step before these). If all of the stacks get an update the deployment...

> > Yesterday on two different occasions and AWS accounts (read: environments) we realised that the redeploy did not actually rerun the deployment event though serverless marked them as successfull...

We actually ended up splitting our single api gateway into multiple ones as described as Method 1 in this article https://seed.run/blog/how-to-share-an-api-domain-between-services-in-a-monorepo-serverless-app.html I had previously been unaware of the possibility for...

> @severi on a different topic, we are exploring ideas for multi-service deployments (in monorepositories). We are looking for feedback on those ideas, it seems it would match your project...

bumped into this issue as well just now and hoping to find some solution to this.

> @severi Any chance you found a solution? I found two options for separating the serverless.ts tsconfig from application code: 1. place the serverless.ts file to a separate ”deployment” folder...

Hey, I added a PR related to this as the lack of proper error logging has been the number 1 annoyance I have experienced when trying out DSPy for the...