Skip to content
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

Update Error: Only one resolver is allowed per field #3

Open
rraczae opened this issue Jun 14, 2021 · 2 comments
Open

Update Error: Only one resolver is allowed per field #3

rraczae opened this issue Jun 14, 2021 · 2 comments

Comments

@rraczae
Copy link

rraczae commented Jun 14, 2021

Hey Guys!

Thanks for the transformer, great idea and approach. We are trying to add a custom transformer to a datasource that was already pushed with the default amplify resolvers. Now we are getting the error:

Resource Name: QueryListTodosPipelineResolver (AWS::AppSync::Resolver)
Event Type: create
Reason: Only one resolver is allowed per field. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: ...; Proxy:
null)

Our workaround was to make a change @model(query: null), then push, then add the transformer and everything works fine. Since this is not viable in a prod scenario, do you have any solutions/suggestions how to handle this?

Cheers!
Rob

@dror-laguna
Copy link
Contributor

dror-laguna commented Jun 29, 2021

Thanks @rraczae for the input...
It seems that this is because of a known Amplify bug: aws/aws-appsync-community#128

I once had it too without using the firehose directive and was able to solve it as described in this comment (like what you did with query: null thing):
aws-amplify/amplify-cli#682 (comment)

@rraczae
Copy link
Author

rraczae commented Jul 6, 2021

Hey @dror-laguna, thanks for the update. Yea it seems like we have to wait for that fix and until then we are creating our custom pipeline resolvers manually through custom templates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants