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
(@aws-cdk/aws-appsync-alpha): Missing AppSync Resolvers #18351
Comments
I'm missing |
|
Hi @otaviomacedo, I've run into this issue again. Is it the intended behavior that I must call |
I think this issue has to do with sym-linking. When I'm developing the construct I'm creating (using npm link), I have to add the |
Also seeing this, This just adds to the schema, doesn't actually add a resolver. api.addQuery("hi", validResolverField) This adds a resolver correctly, but not the schema
|
Figured it out: If your A quick fix was to run or force it // @ts-ignore
!obj.resolvers && obj.generateResolver(api2, "hi3", field.fieldOptions); Longer term would probably update |
I think this PR: #19491 has resolved this issue. I've tested it out and it works for me. Closing. |
|
I doubt that change fixes the issue I was seeing. I've been working on 2.20 for a while. The PR was pushed in 2.18. https://github.com/aws/aws-cdk/releases/tag/v2.18.0 We'll see if it comes back up. |
Oh interesting. Definitely open up another issue if you experience the issue again. |
General Issue
Missing AppSync Resolvers
The Question
The following CDK construct follows the documentation in how to create a GQL API but the resolvers are not being created:
Related CloudFormation created. Notice there is no AWS::AppSync:Resolver resource created.
CDK CLI Version
2.5.0 (build 0951122)
Framework Version
2.5.0
Node.js Version
14.18.2
OS
macOS
Language
Typescript
Language Version
4.5.4
Other information
No response
The text was updated successfully, but these errors were encountered: