Publish function if lambda code changes

[abargnesi]

Currently with version 2.3.2 I cannot publish a new version if only the lambda code package changes.

When we release our project we set publish to true and forceUpdate to false. We do not want to force update because that will deploy and publish new version even when the code/config have not changed.

What I propose is to additionally publish a new version if publish is true and the code package has been updated due to checksum differences.

Edit:

My motivation is production deployments only when there are actual λ code / config changes. Otherwise publishing different versions with the same effective config/code is redundant and confusing later.

[SeanRoy]

Sounds good. Were you planning to submit a PR?

[abargnesi]

Sure I will take a crack at it.

[SeanRoy]

It's fine if you weren't, I just needed to know. If you still want to do it please be aware of the other PR that is touching some of the same code areas.