@aws-cdk/aws-appsync-alpha: Issue defining resolver caching keys

Describe the bug

I enabled PER_RESOLVER_CACHING for my appsync graphql api. I tried to defined a caching config for new Resolver, but the cachingKeys are not getting deployed.

const resolver = new Resolver(scope, `Resolver`,
  {
    ...config,
    api: this,
    cachingConfig: {
      ttl: Duration.seconds(3600),
      cachingKeys: ['$context.identity.claims.https://domain:prop'],
    },
  }
);

Expected Behavior

The resolver gets deployed as i have a valid cachingKey defined $context.identity.claims.https://domain:prop

Current Behavior

Deployment of stack crashes with Error Caching keys need to start with $context.args, $context.arguments, $context.identity, or $context.source. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: 37982d8a-0e08-4a7c-b4b5-35be0a001569; Proxy: null)

Reproduction Steps

Just try to define a resolver like i did.

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.25.0

Framework Version

2.25.0

Node.js Version

v16.13.1

OS

Windows 10

Language

Typescript

Language Version

4.5.4

Other information

Same issue reported here https://github.com/aws/aws-appsync-community/issues/202

[otaviomacedo]

Yes, I’m afraid that’s a limitation on the AppSync side. I’m closing this, as there is nothing we can do on the CDK side. Feel free to reopen it if anything changes.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.