Support for specifying the created lambda 'description' property in config.json

Love Chalice!

One thing I've noticed is all my lambda's created with the Chalice application have the description set to `-`.

Is there appetite for adding support for a description field in the `config.json` that'd map to the created lambda function? At both the global and stage level?

Cheers


Start by tracing how config.json is read and how Chalice creates Lambda functions. Confirm where global and stage-level configuration are handled, then verify that the configured description reaches the created Lambda function at both scopes.

Written by the indexing model from the issue text.