-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
authenticationType AWS_LAMBDA Doesn't work #148
Comments
It would need to be implemented here. I would need to look into amplify-cli to see how it works. Will keep you updated. If you wanted to have a go at this, a PR is also welcome 🙂 |
Hi @bboure Thank you! |
Sorry @Ajvj There have been quite some changes recently in the was package. I guess it requires a bump, but we need to make sure that it stays compatible and works. Unfortunately, I haven't had time recently to work on this library; but if anyone is willing to look into this and open a PR, I'd be happy to have a look at it. |
Any updates on that? It's the show stopper for us to use AppSync because we would need to use AWS_LAMBA auth and there is no way to run it locally. |
I also don't see any way to use authenticationType AWS_IAM. Can you help or give me some information about this? Thank you! |
** Does your functional requirement relate to the problem? Please describe it. **
Lamda is new to AppSync authentication, serverless-appsync-plugin supports it, but serverless-appsync-simulator does not.
Since amplify is already supported, can I import it?
aws-amplify/amplify-cli#7963
Thank you !
The text was updated successfully, but these errors were encountered: