createdAt, updatedAt and id should not be required on inputs / mutations

[malcomm]

Note: This is a blocker.

Describe the bug

Given the following sample schema:

type Foo
  @model
  @key(fields: ["id", "updatedAt"])
{
  id: ID!,
  updatedAt: AWSDateTime!

In order to create/update a Foo, I am required to supply an updatedAt:

    const input: UpdateFooInput = {
      id: this.foo.id,
      updatedAt: moment().toISOString()
    };

    const input: CreateFooInput = {
      updatedAt: moment().toISOString()
    };

createAt and updatedAt should not be required. I'm OK with them being optional, but I can see an argument for them to be treated as special and not messed with at all.

Amplify CLI Version

4.13.1

To Reproduce

Create a model with above primary index with a sort key.

Expected behavior

createAt and updatedAt should not be required.

Additional context
aws-amplify/amplify-cli#401
aws-amplify/amplify-cli#3347

[SwaySway]

Hello @malcomm
These fields are normally not mandatory however when you add @key the fields listed in that directive then become mandatory. Since we do auto-populate the fields for id, createdAt, and updatedAt we can potentially add these in a whitelist when adding @key so they are not set to non-nullable.

[malcomm]

Should also consider this field: __typeName. My thinking is that it also should be in the whitelist?

[hirochachacha]

This is aws-amplify/amplify-cli#1657. That's the reason I made https://github.com/hirochachacha/graphql-auto-transformer. @malcomm Perhaps, it might help you as a temporary solution.

[renebrandel]

This issue is addressed now. Given this schema:

type Note @model @auth(rules: [
  { allow: public, operations: [read] },
  { allow: owner }]) {
  id: ID! @primaryKey(sortKeyFields: ["createdAt"])
  title: String
  content: String @index
  createdAt: AWSDateTime!
}

The mutation request went through: