Enforce one field based on another - kebab-case example

[verneleem]

There are two ways I see around this.

1. Inside the lambda perform the mutation using DQL which bypasses all auth rules.
2. Inside the lambda override the authHeader with your own JWT that passes the add rule.

@gja

graphql will automatically pass along the authHeader, so the security context is the same. However, you can override the security context by passing in the authHeaders explicitly. Before the above bug was fixed, this behaved as an unauthenticated request, so you would not have gotten back any data.