8 ms·

It seems dead? https://github.com/aws/chalice/issues/2067 https://github.com/aws/chalice/issues/2067

• abrichr 2y ago
  > It seems aws focus is now at https://github.com/aws-powertools/powertools-lambda-python https://github.com/aws-powertools/powertools-lambda-python
  • jacky2wong 2y ago
    Surprised to see the list of companies using AWS powertools
  • kapilvt 2y ago
    its not quite the same, roughly 60-70% of chalice code by volume is actually helping auto provision. power tools is about 70-80% code by volume is integration with other services/capabilities in aws (tracing, logging, metrics, etc). the overlap is the event routing shims/decorators.
• tedmiston 2y ago
  Not a huge surprise. It filled a weird niche, which was very easy to use for basic use cases, but Chalice only supported a small subset of Lambda features and didn't get much attention from AWS either. As soon as you tried to do slightly more than was possible with it, it become unviable to manage all of the Lambdas and you end up having to use Terraform or similar anyway. If I were doing lots of new Lambdas today, I'd probably just use a third-party Terraform module for all of it.
• tedivm 2y ago
  Yup! I used to use it, but was very disappointed in how little support it got and ended up dropping it. It's a great idea but never got enough resources to take off.