-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
feat(appsync): support appsync functions for pipelineConfig #10111
Conversation
…asing" This reverts commit f3c77e3.
…s-cdk into appsync-functions
Fellow Bryan here :) any thoughts on what this needs to get merged and released? |
@bryan-hunter Hi Bryan! I think the meat of the work is done, just waiting for a review at this point! It's a big PR, which is totally on me. But I saw some discrepancies with the implementation of @MrArnoldPalmer would it be easier if I split this PR with the breaking change refactor and then the new feature of AppSync Functions? |
also looking forward to this release! |
Would be very nice to have this feature! |
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.
@BryanPan342 good 2 go here once conflicts are resolved. Took me a bit to test this out.
woooo thanks @MrArnoldPalmer 😊 yeah sorry this should have been two PR's |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Support AppSync Function by exposing Function Configuration. **BREAKING CHANGES**: `Resolver.pipelineConfig` no longer supports `string[]` - **AppSync**: `Resolver.pipelineConfig` no longer supports `string[]`, instead use `AppsyncFunction` - **AppSync**: Resolvers are scoped from `GraphqlApi` instead of its `Data Source`, this means that the **logical id** of resolvers will change! Fixes aws#9092 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Support AppSync Function by exposing Function Configuration. **BREAKING CHANGES**: `Resolver.pipelineConfig` no longer supports `string[]` - **AppSync**: `Resolver.pipelineConfig` no longer supports `string[]`, instead use `AppsyncFunction` - **AppSync**: Resolvers are scoped from `GraphqlApi` instead of its `Data Source`, this means that the **logical id** of resolvers will change! Fixes aws#9092 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Support AppSync Function by exposing Function Configuration.
BREAKING CHANGES:
Resolver.pipelineConfig
no longer supportsstring[]
Resolver.pipelineConfig
no longer supportsstring[]
, instead useAppsyncFunction
GraphqlApi
instead of itsData Source
, this means that the logical id of resolvers will change!Fixes #9092
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license