Also a general serverless question, we have around 7 microservices, which we have now moved under a monorepo and now deploying via seed and life seems easy. Also we use lambda layers. Now earlier, if there was some common code, we used to have a separate repo for it and release it in a private python package repository. and whenever we updated that, we used to update a lambda layer and deploy all our microservices (which ever needed it) Now after moving the seed we have couple of options 1. Have a separate repo anytime code is updated release it in package repository. Also we use a package called serverless latest layers so i dont need to change the versions just need to update all our services. 2. another option is inside our monorepo, have a separate service for layers where we write code which are used across our microservices, somehow export it as layer and use its output in microservices. Seed anyways reploys a service if the code is changed, so it will create it once for each branch and update only when changes are there. But not that much clear work flow wise, So general question is how to share

python

code across monorepo in a serverless setup.

@Sourav Sarkar, if you decide to go with the 1st option, I just wanted to point out that after you upload a new layer, you can use SEED cli to trigger a deploy in your microservice app. For 2, how are you sharing the layer with the other microservice? (ie. are you exporting the layer arn in the layer service, and importing the arn in rest of the stacks?)