Skip to content

Issues: eventuate-clients/eventuate-aws-gateway-serverless-plugin

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.

Sign up for GitHub

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

8 Open 0 Closed
8 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Update the Serverless plugin to allow to specify a DLQ
#8 opened Aug 7, 2017 by dartvandru
gatewayConfigChanged is flakey?
#7 opened Aug 3, 2017 by cer
5
Gateway should show headers when the server-side fails enhancement
#6 opened Aug 3, 2017 by cer
1
Plugin should show function names as well as gateway ids during "serverless deploy" enhancement
#5 opened Aug 3, 2017 by cer
1
Plugin-specific AWS credentials enhancement
#4 opened Jul 22, 2017 by cer
Use serverless configuration mechanism rather than relying on environment variables enhancement
#3 opened Jul 22, 2017 by cer
sls commands should take a -f functionName argument as an alternative to a --gatewayId enhancement
#2 opened Jul 22, 2017 by cer
sls gateway info should list information about lambda's gateways enhancement
#1 opened Jul 22, 2017 by cer
1
ProTip! no:milestone will show everything without a milestone.