Developer can add VTL resolver to be executed before/after specific graphQL requests. Question is, is there a way to "slot" (attach) VTL resolver that would be executed with any graphQL request, not just specific one? Currently, I place Mutation.createTodo.postAuth.2.req.vtl and it would be executed after amplify-generated Mutation.createTodo.postAuth.1.req.vtl, but I need another mutation.some-other-request.postAuth.2.req.vtl file (with same contents) to be execured after mutation.some-other-request.postAuth.1.req.vtl This resulting in need of many *.2.req.vtl files of exact same content for each mutation/request.
What I have tried: looking into AWS docs: "Amplify generates AWS AppSync pipeline resolvers for your queries and mutations. You can "slot" in your custom business logic between Amplify-generated resolvers. You can find Amplify-generated resolvers under your API resources' build/resolvers/ folder. The resolver functions file name determines its placement within the slot sequence." (https://docs.amplify.aws/cli/graphql/custom-business-logic/#override-amplify-generated-resolvers)
Also, Override Amplify-generated AppSync resources at https://docs.amplify.aws/cli/graphql/override/
I ended up duplicating same vtl to be placed in slot 2 of every resolver, which seems hacky and as an walkaround
