Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
packages/serverless/lib/plugins/aws/appsync/resources/MappingTemplate.js
Dismissed
Show dismissed
Hide dismissed
# Conflicts: # package-lock.json # packages/serverless/package.json
There was a problem hiding this comment.
@czubocha Looks good. Glad we finally did this. Huge thanks to the original AppSync contributors! My only question is, how does the "migration" look like for users to move out of the plugin? Do they just have to comment it out and remove it from package.json? Maybe this should be in the docs.
Thanks! Yes, exactly - the migration steps are covered in the docs. Users just need to remove the plugin from There's a dedicated “Migration from the community plugin” section here: |
3 participants
Summary
This Pull Request integrates the previously standalone AWS AppSync plugin functionality directly into the Serverless Framework core. By migrating this support into the main repository, AWS AppSync becomes a native feature, providing a more seamless experience with built-in command support, consolidated documentation, and simplified dependency management.
Main Changes:
serverless-appsync-pluginsource code and logic into the core Framework as a native AWS provider plugin.serverlessCLI.ajv-merge-patchdependency to simplify internal validation logic.