Lambda not deployed correctly when the name of the function changes

Today I had a problem while deploying a lambda function.

I have a module defined in `chalicelib/internal/parses` which used to define an S3 triggered lambda called parser. The lambda is registered on a blueprint, which is then imported in the main file and registered to the application.

Today I renamed the `parser` function to `object_parser` and redeployed my lambda. When executing it I got the following error: `Runtime.HandlerNotFound: Handler 'parser' missing on module 'chalicelib.internal.parser'`.
It almost seem that the code is still looking for the old function.
In past I had a similar problem when moving a lambda function from the main file to a module and register it via blueprint.

Am I doing something wrong or is this a bug?

Thanks in advance,
Luca

Reproduce the deployment using the module in chalicelib/internal/parses, the blueprint registration, and the main file that registers the blueprint. Inspect which handler name is emitted after renaming parser to object_parser; done means a fresh deployment invokes the renamed Lambda without referring to parser.

Written by the indexing model from the issue text.