New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need a way of running the Lambda service locally #22
Comments
I agree, thanks for the feature request. This is something I plan on adding. |
👍 |
1 similar comment
👍 |
👍🏻 |
yes! please do, i boiler-plated it under flask, but it flask uses <> brackets for url params and accesses url params differently - bleh wasted 2 hours. something please! soon please! |
Yes! And I wanna create custom class to execute just like |
this is super urgent for IRL usage of this framework, deploying takes forever and error messages in remote logs are super generic (no exception propagation) |
This command will spin up a local http server that you can use to run your chalice apps. The intent is to provide a quicker feedback loop while developing your code. Previously you would have to deploy to API gateway in order to test changes to your API. There's one main feature that's missing from chalice local: this does not try to assume the role that's associated with lambda function. In order to do this, we'll likely need to update the trust policy of the role to give the AWS user being used locally the ability to assume the role. Not exactly sure how I want this to work so I haven't added that as part of this commit. Closes aws#22.
#147 has been merged, which adds support for Btw, the rationale for not propagating exceptions by default is so that you don't leak internal information in your error responses. You can set That being said, hopefully |
This would be great for testing and iterating locally, vs deploying and then validating.
(I couldn't find any references to this in the docs or source code, so apologies if this is already a feature)
The text was updated successfully, but these errors were encountered: