Starred. This looks fantastic. I've been exploring lambda deployment options for my new Alexa skills kit library, since Amz pushes lambda.<p><a href="https://github.com/johnwheeler/flask-ask" rel="nofollow">https://github.com/johnwheeler/flask-ask</a>.<p>Can you please explain any differences over Zappa and if you're deploying flask?<p>Oh, and the project name is oh so damn cool.
If you're interested in dirt simple Lambda deployment, check out Kappa[0], written by the same person as boto.<p>Gordon looks interesting and I'm definitely going to check it out, but from what I can tell, one of the downsides is that it uses CF.<p>Don't get me wrong, I love CF for it's reproducibility, but waiting for a CF stack to run on every deploy will be frustrating for rapid iteration. CF is great for managing your infrastructure once you have a good idea of how it should look and aren't making constant changes anymore.<p>I suspect my workflow will be something like using Kappa while I'm iterating, and then using Gordon for the final deployment once it looks like everything is working as expected.<p>[0] <a href="https://github.com/garnaat/kappa" rel="nofollow">https://github.com/garnaat/kappa</a>
This looks great.<p>I'm particularly excited about the CloudFormation support.<p>If you're managing stuff on AWS without CloudFormation you're missin out on one of the most powerful features of the platform.<p>CF can be pretty hard to use, which is why I love seeing OSS projects that solved the tedious parts of it for all of us to use.
This is great. I wish this was around 8 months ago when I built lambda infrastructure at Cronitor. Local invocation, multi region deploys and config management all took far too much development time.