feat(appsync): add ApiCache L2 construct and addCache method

[TonySherman]

Issue # (if applicable)

#31160
Closes #.

Reason for this change

Description of changes

Adds L2 Construct for ApiCache on AppSync graphQL Apis
and a method to add a cache to existing graphQL Api constructs.

Description of how you validated changes

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[pahud]

If you are implementing the ApiCache L2, I suggest you first read the design guidelines here and read other existing L2 constructs to learn the patterns.

Generally, if you are creating a L2 construct called Foo. You should:

1. Define IFoo interface for it that extends IResource.
2. Define Foo construct class that extends Resources implements IFoo
3. Define FooProps as the construct props for Foo

In addition to the design guides and existing L2 constructs, I would recommend you read this blog post in which I shared how I built an Agent L2 construct.

[pahud]

L2 construct should extends Resource implements IApiCache. You should export IApiCache as well.

[pahud]

I think it should be

readonly api: IGraphqlApi;

Pull request has been modified.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: cee7b83
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[pahud]

Some suggested changes here:

• Validation for Ttl property:

1. The CloudFormation documentation specifies that the Ttl property should be a number between 1 and 3,600 (inclusive). You can add some validation to ensure that the provided ttl value is within this range.
   You can add a check in the constructor of the ApiCache class to validate the ttl value:

constructor(scope: Construct, id: string, props: ApiCacheProps) {
  super(scope, id);

  if (props.ttl < 1 || props.ttl > 3600) {
    throw new Error('Ttl value must be between 1 and 3,600 seconds');
  }

  new CfnApiCache(this, 'Resource', {
    // Rest of the code
  });
}

[TonySherman]

Some suggested changes here:

• Validation for Ttl property:

1. The CloudFormation documentation specifies that the Ttl property should be a number between 1 and 3,600 (inclusive). You can add some validation to ensure that the provided ttl value is within this range.
   You can add a check in the constructor of the ApiCache class to validate the ttl value:

constructor(scope: Construct, id: string, props: ApiCacheProps) {
  super(scope, id);

  if (props.ttl < 1 || props.ttl > 3600) {
    throw new Error('Ttl value must be between 1 and 3,600 seconds');
  }

  new CfnApiCache(this, 'Resource', {
    // Rest of the code
  });
}

Thanks! Sorry for the delay on updates to this work. Got sidetracked with some other stuff and I'll be getting back to this shortly.

[aws-cdk-automation]

This PR has been in the MERGE CONFLICTS state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week.

[aws-cdk-automation]

This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.