Support new Lambda deployment params: Provisioned Concurrency, Maximum Event Age and Maximum Retry Attempts
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
New and quite exciting Lambda configuration parameters have been recently announced by AWS:
- https://aws.amazon.com/ru/about-aws/whats-new/2019/11/aws-lambda-supports-max-retry-attempts-event-age-asynchronous-invocations/
- https://aws.amazon.com/ru/about-aws/whats-new/2019/12/aws-lambda-announces-provisioned-concurrency/
They can be set using AWS console and it would be great to have them configurable in .chalice/config.json as well:
> 
Contributor guide
Research direction
Start with .chalice/config.json and trace how Lambda deployment configuration is read and sent to AWS. Confirm how Provisioned Concurrency, Maximum Event Age, and Maximum Retry Attempts should be represented, then verify that each parameter can be configured and applied during deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100