publish version when updating lambda code

[mtrbean]

I think it's handy to be able to optionally enable lambda code versioning (essentially setting publish=True when updating lambda function). This allows people to do a quick manually rollback if anything goes wrong.

[jamesls]

Hi, sorry about the delay here. I'd like to hear more about this use case. This was something that was considered a while ago (#20), and I think there might have been a branch that implemented that around here somewhere. The thing that I found is that it gets problematic if you manually roll back via versioning/aliasing outside of chalice then it's easy to get out of sync with what you have locally in your git repo vs. what's actually running on lambda. Taking into account we now support multi lambda functions (which are all deployed together as part of chalice deploy) as well as things that are dependent on the code in your lambda function (e.g the auto policy generation which scans your source code), it seemed more straightforward to just rollforward a change (i.e revert a commit in your git repo and rerun chalice deploy). That combined with stages made it easier to test out changes before deploying to prod.

Open to suggestions though, would be interested in any use cases I'm missing.

[stealthycoin]

Closing due to inactivity. Feel free to reopen this to share your use case with us.