Problem when using multiple authorisation annotations with implements keyword

[HannaSanford]

I have a schema with interface types which uses the AppSync multiple authorisation method annotations on some types, mutations, and queries.

For example:

type ReadingTask implements Task @aws_cognito_user_pools @aws_iam {
    id: ID!
    patientId: ID!
    organisationId: ID
    readingId: ID
    reminders: [String]
    status: TaskStatus!
    subtitle: String
    time: String!
    timeAndId: String!
    title: String!
    vital: VitalType!
}

when this schema is deployed by the serverless plugin, these types come through with the annotations before the implementation. i.e.

type ReadingTask @aws_cognito_user_pools @aws_iam implements Task {
    id: ID!
    patientId: ID!
    organisationId: ID
    readingId: ID
    reminders: [String]
    status: TaskStatus!
    subtitle: String
    time: String!
    timeAndId: String!
    title: String!
    vital: VitalType!
}

This is flagging up as an invalid schema and breaking the related queries and mutations.
Currently, I am having to manually change these in the AppSync console and re-add the related resolvers.

[HannaSanford]

This is still happening and it is incredibly problematic as it reverts every time I push new changes to my schema.

[bboure]

@HannaSanford Sorry for late attention.

The validation of the schema relies on the graphql package.
I realize that we are far behind in term of version.

I am not sure though if upgrading to the latest version of graphql would solve the issue.

Could you try and give us some feedback?

An alternative (if that does not work), would be to introduce an option to disable schema validation.

[bboure]

@HannaSanford I am not able to reproduce this issue. Is this still happening?

If I understand correctly, your schema file has the annotations after the implements, but when deploying it goes after, making it invalid ?

Could you give more details like:

• is the error thrown by the plugin itself or by CloudFormation/AppSync?
• version of the plugin
• are you using schema stitching?
• can check in the .serverless directory in the generated cloudformation stack the content of GraphQlSchema.Properties.Definition and if it is correct or not?