-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support swagger file to serve APIs (external & internal) #101
Comments
I think this is a combination of two things:
|
Hey @johnewart - just a heads up that #83 is now merged. |
We've just merged #222 - this adds support for Swagger definitions to load mounts in the router. I've tested this with inline Swagger templates. |
I've just released v0.2.3 to npm which includes this. |
I asked this on Stackoverflow too but not much of a response. I think aws-sam-local is still a little new.
I've got a simple project. The basic setup is like this...
I run gulp and I end up with a
build
folder. It looks something like this...The build works great. I want to run it locally rather than uploading the ZIP to lambda and the client directory to S3 every time I make a change.
To do this I'm running aws-sam-local. Yes I have
docker
installed and running. From the project folder I run this...Now I can go to my browser and visit http://localhost:3000/ to see things. As expected my static files (index.html) load up just fine. But when I try to access an API route http://localhost:3000/test I get a 404.
My sam.yaml
My swagger.yaml
How can I get aws-sam-local to run my lambda API?
The text was updated successfully, but these errors were encountered: