Cannot add createdAt in @key fields without making it available as part of mutation

[darshannahar]

Describe the bug
With @model directive createdAt is an autogenerated column in DynamoDB. I want to use it as a sort key. But I do not want to make it available in the mutation input. But amplify forces me to add createdAt as a part of the type and thus makes it available in mutation input.

Amplify CLI Version
4.20.0

To Reproduce
Graphql schema of below type won't be accepted:

type Comment @model @key(fields: ["blogId", "createdAt"]) {
  id: ID!
  content: String!
  blogId: ID!
  blog: Blog! @connection(fields: ["blogId"])
  customerId: ID!
}

Expected behavior
Should allow auto-added columns like createdAt, updatedAt to be part of key

Desktop (please complete the following information):

• OS: Mac
• Node Version- 14.2.0

[dtelaroli]

+1

Same for ID

[darshannahar]

Found this issue to be duplicate of #1657

[ammarkarachi]

@darshannahar we have a PR linked above closing it as it is a duplicate

[yuth]

This fix is released in Amplify CLI v4.21.1

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.