@bfieber, thanks for sharing!
Actually, I have another related question with that regard.
As you mentioned, serverless creates deployment package files under: deploymentBucket/serverless////
I was thinking, if we can leverage as a version for CI/CD purpose. So, when CF stack with actual Lambda(s) code is tested and confirmed, instead of making new deployment, we can ‘promote’ exactly the same package to another env (e.g. TEST -> PROD). So, my question is if this value is available in run-timw during deployment, so we can hook up to deployment pipeline and persist it as a service version. And assuming we have it, is there any way (plugin?) to just get it deployed from remote S3 folder. I know, there is an option to create actual deployment package is sls locally, and get it deployed as a next step. But, just curious, if we can do the same with S3.
I’d appreciate your thoughts on that.