-
Notifications
You must be signed in to change notification settings - Fork 183
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
Feature Request: Merged Api Support #605
Comments
Thank you @SethO This is something I want to support.
My first impression is that we should probably not do that. I will try to find some time to investigate all this. |
I've got a working GitHub example of the CloudFormation here. There are mistakes in the current AWS CFN documentation that I'll highlight in an upcoming blog article on the subject (with links to this repo, I might add). I'll post a link in this thread when it's published. |
Here is the blog post. |
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.
The text was updated successfully, but these errors were encountered: