Skip to content
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

Closed
marvinpinto opened this issue Jul 11, 2016 · 8 comments
Closed

Need a way of running the Lambda service locally #22

marvinpinto opened this issue Jul 11, 2016 · 8 comments

Comments

@marvinpinto
Copy link

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)

@jamesls
Copy link
Member

jamesls commented Jul 11, 2016

I agree, thanks for the feature request. This is something I plan on adding.

@jvkumar
Copy link

jvkumar commented Jul 12, 2016

👍

1 similar comment
@moselaymd
Copy link

👍

@dannymcpherson
Copy link

👍🏻

@dkotik
Copy link

dkotik commented Jul 19, 2016

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!

@kousuke-takeuchi
Copy link

Yes! And I wanna create custom class to execute just like python app.py runserver or python app.py test --with-report

@sscarduzio
Copy link

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)

jamesls added a commit to jamesls/chalice that referenced this issue Oct 27, 2016
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.
@jamesls
Copy link
Member

jamesls commented Oct 27, 2016

#147 has been merged, which adds support for chalice local. I'll have a release out soon, try it out and let me know if you have any feedback.

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 app.debug = True in your app.py file, and the exceptions will propagate back to you.

That being said, hopefully chalice local makes this unnecessary :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants