@default directive to work even when field level resolver do have create permission

[sushpatg]

Describe the feature you'd like to request

Sample Schema

  type Todo @model @auth(rules: [{allow: owner, identityClaim: "sub", operations: [read,create]}]) {
  id: ID! @primaryKey @auth(rules: [{allow: owner, identityClaim: "sub", operations: [read, create, update]}])
owner: String! @auth(rules: [{allow: owner, identityClaim: "sub", operations: [read, create]}])
  status: String @default(value: "test") @auth(rules: [{allow: owner, identityClaim: "sub", operations: [read]}])
}

Use-Case: Users should be able to create records and the status filed should populate with default value. The restriction is that users, should not be able to pass or update the status value.

The above auth rules are failing with "Unauthorized on [status]" error.

Describe the solution you'd like

To be able to populate the default value to status filed without giving create permission

Describe alternatives you've considered

Current work around: Override Amplify-generated resolvers to update the Mutation.createTodo.init.2.req.vtl resolver to return unauthorized if id value is passed

## [Start] Setting "status" to default value of "test". **
#if( $util.isNull($context.args.input.status))
$util.qr($context.args.input.put("status", $util.defaultIfNull($ctx.args.input.status, "test")))
#else
$util.unauthorized()
#end
## [End] Setting "status" to default value of "test". **
{}

And also adding "status" to ownerAllowedFields0 in Mutation.createClaim.auth.1.req.vtl

Additional context

Similar Github Issue: 9846

Is this something that you'd be interested in working on?

• [ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

• [ ] ⚠️ This feature might incur a breaking change

[AnilMaktala]

Hi @sushpatg, Thank you for raising this. We will categorize this as a feature request for our team to investigate and assess more thoroughly.