sid88in / sid88in/serverless-appsync-plugin
Feature Request: Merged Api Support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 955
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Description
I wanted to start a discussion about how this project evolves given the newly available AppSync Merged APIs.
One approach could be to use one API definition per source API and one for the merged API. The last would be a convenient "wrapper" over the CloudFormation needed to set one up.
Another approach could be something closer to what v1 of this plugin supported where we define multiple APIs in the same definition and then include the merged API to stitch it all together.
I look forward to the conversation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies no files, tests, or entry points. First clarify whether merged APIs should use separate API definitions with a CloudFormation wrapper or a multi-API definition, then define the expected configuration and acceptance criteria before locating the implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, graphql, typescript
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100