-
-
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
Support serverless-appsync-plugin
v2
#183
Conversation
Update dependencies
fix: revert to update `globby`
serverless-appsync-plugin
v2serverless-appsync-plugin
v2
Rewrite by TypeScript and update to support `serverless-appsync-plugin` for v2
serverless-appsync-plugin
v2serverless-appsync-plugin
v2
I can run |
serverless-appsync-plugin
v2serverless-appsync-plugin
v2
Thank you @horiuchi I will have a look at this asap. I was considering deprecating this package though and offer other solutions. |
Thank you @bboure for the reply. I don't seem to have any problems with my usage, but what concerns do you have? |
No concern at all. My goal is to make the serverless-appsync-plugin itself evolve toward this strategy. |
I see. But in practice, the only way to debug AppSync is to use serverless offline. However, I think there is an option not to merge this change because it is incompatible with the previous version. |
I think we can version bump this package to v2 with your changes (skipping v1, to align it with the version of the main plugin). |
@bboure When will this PR be merged and published to npm? |
We also depends on this here, do you think you could release this? |
@horiuchi I tried the source branch on my local and I'm getting
First how can I turn on verbose debug? SLS_DEBUG=* and DEBUG=* doesnt do anything for me 😕 |
@Hideman85 Thank you for trying this. Setting However, this error probably occurs when loading the config, so there is no additional information. |
Hey thanks for getting back to me. I checked and the logging is really poor even with First issue Last point, the update to support v2 is incomplete, v2 allow inline data source and here again, the config is fine it fails at starting up the appsync simulator with In the end I ended up to refactor our serverless.yml to ts version with helper function to create the resources correctly, so then I handle validation myself at config before anything start up. It becomes a lot clearer than the errors thrown today. Wasnt really fun but now our team is safer and ready to go v2 with JsResolvers (good thing is we could support ourself bundling on the fly the js resolvers then). |
@bboure Sorry to disturb you, have you considered merging this fix for now? Right now I'm using the fork in our flow and this add quite some overhead in our process. This would be awesome to have this released 🙏 |
|
||
exports[`resolveConfiguration should generate a valid config 2`] = ` | ||
{ | ||
"apiKey": "0123456789", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no multiple key ?
I am getting 'Duplicate "graphql" modules cannot be used at the same time' error when using the changes from this pr. Anyone else facing the same issue? |
@horiuchi Thank you for the generous work here. I have also tried this branch and ran in to an issue. I will try to come back here and provide a fix or commit but time is limited at this moment so I will just report a bug. I wonder if there is interest in having this version funded? Although simulator is not perfect, it provides us with a way to debug resolvers locally which is much more efficient than deploying and logging. This is a very helpful package. Perhaps there are ways to do it in the cloud; it seems like a mystery to me. output
serverless.yml (relevant example)
|
@dsiebes Did you figure out that issue? |
@Karjan1 |
@bboure will this be merged and deployed? I understand you wish to deprecate but a lot of people (including the company i work for) rely very heavily on it Thanks for all the work you and your contributors have put in! : ) |
is the "code" feature with js runtime working ? |
Sorry all for not taking enough consideration on this topic. The AppSync ecosystem evolves very fast and I'm having trouble keeping up with everything :-( @horiuchi have you been maintaining this PR (or anything else) to keep it in sync with both the changes that happened in the v2 of the main plugin and the updates that amplify received? I'd be happy to help release a v2 of this plugin to unlock everyone who is blocked by this. |
No updates have been made since this PR was created. However, if there is any problem with merging this PR, I would like to support it. |
Thank you for your update @horiuchi I will have a look again at this, but I have not followed updates on the amplify simulator which is a big dependency of this package. Have you been using this in your day-to-day work? Do. Do you have enough confidence that it works? I'd suggest we open a v2 (or v1 since it is currently in v0) as a beta on the '@next` channel and start collecting feedback. |
I don't use it myself at all these days. I agree with the release as a beta. |
Thanks for your work ! I still use the v1 in my day to day work. We plan to switch to the v2 and I would be happy to get involved for the v2 of the simulator. |
I've been using it in my day-do-day work for about a month, it works properly except for pipeline functions. I've opened a PR to @horiuchi 's repo to fix that issue |
Handle pipelines
2c8de23
to
dbc1872
Compare
@bboure If the v2 still planned, can we help one way or another ? |
@plezan Unfortunately, I was not able to follow up on this. If that helps, I can invite a few volunteers as maintainers to this repo to help keep the ball rolling. |
@bboure I would be happy to help keeping this repo moving forward. |
@plezan I have added you and @horiuchi as maintainers. This project uses semantic-release. (Also see here) I'd recommend creating a pre-release (next) for this PR. If you have any questions, let me know. |
Thank you for inviting me to be a maintainer. But What should I do as a maintainer? |
@horiuchi Don't worry. There is no obligation of anything. |
🎉 This PR is included in version 1.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Amazing! Good job @plezan ! 🙏 |
This PR is a rewrite to work this plugin with serverless-appsync-plugin version 2.
This change is incompatible with previous version because the serverless-appsync-plugin configuration is not compatible with version 1.
And, I have rewritten it in TypeScript. The existing functionality is still there.
#178