feat(trigger): Allow trigger to work with Lambda functions with long timeouts

[DerkSchooltink]

Reopened PR from #23650 and #23788

And re-revert from #23062 (v2.61.1)

Implements #23058 and fixes #23407

Worked on comments from @TheRealAmazonKendra as well. Added an integration test scenario where a Lambda function will be triggered by a Trigger construct, send a message to an SQS queue, which will be consumed by the integration test assertion.

[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. Dissmissing previous PRLinter review.

[aws-cdk-automation]

This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state.

[DerkSchooltink]

I might be wrong, but the build failure doesn't seem to be related to my changes:

FAIL test/resource-pool.test.js
@aws-cdk-testing/cli-integ:   â—� double dispose throws
@aws-cdk-testing/cli-integ:     expect(received).toThrow()
@aws-cdk-testing/cli-integ:     Received function did not throw
@aws-cdk-testing/cli-integ:       33 |
@aws-cdk-testing/cli-integ:       34 |   await lease.dispose();
@aws-cdk-testing/cli-integ:     > 35 |   expect(() => lease.dispose()).toThrow();
@aws-cdk-testing/cli-integ:          |                                 ^
@aws-cdk-testing/cli-integ:       36 | });
@aws-cdk-testing/cli-integ:       37 |
@aws-cdk-testing/cli-integ:       38 | test('somewhat balance', async () => {
@aws-cdk-testing/cli-integ:       at Object.<anonymous> (test/resource-pool.test.ts:35:33)
@aws-cdk-testing/cli-integ:   â—� somewhat balance
@aws-cdk-testing/cli-integ:     Calling dispose() on an already-disposed lease.
@aws-cdk-testing/cli-integ:       93 |       dispose: async () => {
@aws-cdk-testing/cli-integ:       94 |         if (disposed) {
@aws-cdk-testing/cli-integ:     > 95 |           throw new Error('Calling dispose() on an already-disposed lease.');
@aws-cdk-testing/cli-integ:          |                 ^
@aws-cdk-testing/cli-integ:       96 |         }
@aws-cdk-testing/cli-integ:       97 |         disposed = true;
@aws-cdk-testing/cli-integ:       98 |         return this.returnValue(value).finally(() => process.stderr.write(`Lease returned by ${process.pid}: ${value}`));
@aws-cdk-testing/cli-integ:       at Object.dispose (lib/resource-pool.ts:95:17)
@aws-cdk-testing/cli-integ:       at test/resource-pool.test.ts:35:22
@aws-cdk-testing/cli-integ:       at Object.<anonymous> (../../../node_modules/expect/build/toThrowMatchers.js:83:11)
@aws-cdk-testing/cli-integ:       at Object.toThrow (../../../node_modules/expect/build/index.js:382:21)
@aws-cdk-testing/cli-integ:       at Object.<anonymous> (test/resource-pool.test.ts:35:33)

[aws-cdk-automation]

This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state.

[aws-cdk-automation]

This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state.

[aws-cdk-automation]

This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).