This carries on from Best practices for managing several lambda functions?
It’s got to the stage where I need some continuous integration to ensure changes are deployed predictably. I have this script:
#!/bin/bash for i in */ do ( cd "$i" && npm i && npm run deployprod ) done
First off, I probably should have one huge serverless.yml instead of separate lambda functions. WDYT?
Secondly, most painfully, I don’t want to deploy unless something has changed! Else
sls deploy list becomes really hard to follow. Also my deployment stage takes like 5 minutes with the 10 lambdas or so that I have.
Am I missing some tricks to make this a bit more manageable? Did look at https://github.com/search?utf8=✓&q=filename%3A.travis.yml+"sls+deploy"&type=Code but nothing interesting popped up.