You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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)
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.
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
The text was updated successfully, but these errors were encountered: