Comments (19)
Hey Kapil and everyone,
Just wanted to say I hear you and understand the frustration. I'm having discussions internally about this, and I'll update as soon as I have anything to share.
Also, please feel free to continue the comments, this is really helpful feedback.
from chalice.
I have been discussing this with our AWS reps and they just assured me they talked to the team and that work is being done here, so I come to look at the PRs and Issues and see a dumpster fire. I also have a contribution pending on one of those issues that hasn't received a response. The 50MB Zip File limit cripples functionality and I have a working patch that deploys via Docker and ECR.
This is an AWS branded project. I get that this project itself isn't being charged for, but it was put out as a way to adopt paid AWS services and many of us have invested significant time in adoption as well as contributing our time and work back to a for-profit company and all we ask is that you work with us, accept the feedback and free code/consulting we're giving you, and do your due diligence maintaining a project/framework that you put out. You're leaving a lot of hanging here, and after 3 previous attempts at adopting Lambda, if this one gets hosed, I'm not coming back. It has been a bumpy ride over the last several years with Lambda to say the least and you owe it to those of us that have paid with our time, effort and money to finally deliver something that works as it was promised.
from chalice.
I say this, having contributed significant functionality to chalice
https://github.com/aws/chalice/pulls?q=is%3Apr+author%3Akapilt+is%3Aclosed
and adopting it for several projects, I wouldn't recommend it at this point to a new user, due to its overall health, and lack of updates.
from chalice.
I've been talking to my AWS rep about this during our calls. He had me write up a message to share with the team about what we're getting out of Chalice and why we'd like it to stick around. I gather it's future is uncertain and I think having folks make some noise might help at this stage. If you have a business AWS account, I'd encourage you to reach out to your reps. From what I gather, that's the only place we're going to get traction on this as this Github "Issues" is considered "external communicaton" of sorts. If we want this project to stick around, and I do, we are going to have to make sure that the maintainers know we're here.
from chalice.
Hello everybody.
I always follow this project and have great affection for it, for its simplicity and robustness.
However, what always prevented me from adopting it commercially was this aspect of lack of engagement, and lack of evolution.
I did academic work using it, but I was afraid to adopt it commercially and ended up opting for Spring Boot.
https://github.com/limiardigital/idemocracia
But I still follow it, and I hope it becomes a viable competitor, since I've never found this ease and level of integration in a framework.
But that last effort is missing, and some additional integrations and configurations such as: RDS Proxy, OpenAPI, improvements in the configuration and management of the API Gateway and other improvements.
from chalice.
It feels like, in this case no news
means bad news
😢
from chalice.
I worry this is being abandoned. Can anyone recommend a similar alternative which is close to chalice's simplicity (python centric) ? I so love chalice as others are so heavy, but if it can't keep up, it's time to grudgingly move on.
from chalice.
@henryivesjones I feel the same way about the ability to use Docker-based Lambda Functions. The size limit for Zip files is painfully small and I've used the SAM package generation capability, with a process to modify it, to make Chalice deploy via Docker and they can, and very much should, incorporate this functionality into the Chalice main. There are a litany of these minor lift feature requests and maintenance issues that need to be addressed. I don't want to see the project die, but as the Issue Title says, it's time to "fix, archive or fork".
from chalice.
It feels like, in this case
no news
meansbad news
😢
Out of curtesy I'm waiting to post reinvent, most AWS teams are pretty busy atm.
from chalice.
re no movement, on my previous observations on project health from two years ago #1833
from chalice.
And if you're going to abandon this project you at least owe us a heads up so that we can decide whether to abandon as well, or fork it and go our own way.
from chalice.
This project was understaffed since the inception.
I've forked it in 2021 to have at least some features merged, unfortunately, that code was closed source.
It looks like nothing changed....
from chalice.
This project feels dead, many new useful Lambda features have been introduced, but cannot be leveraged with chalice because of a lack of maintenance.
To name a few...
https://aws.amazon.com/blogs/aws/aws-lambda-now-supports-up-to-10-gb-ephemeral-storage/
https://aws.amazon.com/blogs/compute/introducing-maximum-concurrency-of-aws-lambda-functions-when-using-amazon-sqs-as-an-event-source/
Adding these configuration options to chalice is not a very large lift, and could even be done (and have been) by the community, but they will probably never make it to main
because PRs are just sitting there with no engagement from the maintainers.
from chalice.
checkout aws copilot, if your forced to use AWS that seems to be the best they offer at this time..
from chalice.
@bobcolner unfortunately copilot is even worse, and less documentation
from chalice.
Related Issues (20)
- Can't get querystring parameters on connect
- [Proposal] Allow for registration of custom error handlers
- Middleware short circuit does not use app.api.cors setting
- websocket close connection with error code
- Automatic SDK generation not available for apps deployed via AWS CDK
- api_gateway_policy_file no longer works - error
- Support Terraform 1.4 HOT 1
- Unable to Render HTML Page with Chalice and Jinja2
- Why doesn't {proxy+} work as catchall ? HOT 1
- No way to set retry count on event bridge lambda (cron)?
- Support code signing for AWS Lambda
- AWS Chalice: Error on Redeploying @app.on_dynamodb_record Lambda
- Support for arm64 Graviton HOT 1
- Support for SSE streaming (OpenAI support)
- Config `log_retention_in_days` not working HOT 1
- Aws lambda unzipped size error - aws chalice HOT 3
- Update demo Applications to Python 3.10
- HTTPResponse.create_from_dict raise AttributeError when response body is None
- Support Python 3.12 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chalice.