feat: support healthCheckGracePeriod in QueueProcessingFargateService

[TrevorBurnham]

Closes #34220

Reason for this change

QueueProcessingFargateService supports the ECS deployment circuit breaker, but doesn't currently offer any way to configure the health check grace period used by the circuit breaker, as FargateService does. This PR rectifies that discrepancy.

Description of changes

Added the healthCheckGracePeriod property to QueueProcessingFargateService, matching the corresponding property on FargateService.

Describe any new or updated permissions being added

None.

Description of how you validated changes

I've added a unit test to verify that the property is passed to the underlying FargateService.

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]

(This review is outdated)

[TrevorBurnham]

Clarification Request: The PR linter is failing with

Features must contain a change to an integration test file and the resulting snapshot.

I've tried to satisfy this requirement, but the instructions in CONTRIBUTING.md are either incorrect or incomplete.

Here are the steps I went through:

1. Freshly cloned the repo on my Mac
2. Ran yarn install
3. Ran npx lerna run build --skip-nx-cache, which had a failure in the @aws-cdk/cx-api:build target (unrelated I believe)
4. Ran cd packages/aws-cdk-lib && yarn test, where every test failed with errors like Cannot find module '../dist/core/cfn-utils-provider.generated' from 'core/lib/private/cfn-utils-provider.ts'
5. Ran cd packages/@aws-cdk-testing/framework-integ && yarn integ test/aws-ecs-patterns/test/fargate/integ.queue-processing-fargate-service-grace-period.js --update-on-failed, which gave me "No such integ test".

The test failures suggest that the build is incomplete, despite me running the build command as described in CONTRIBUTING.md.

[shikha372]

te, despite me running the build command as described in CONTRIBUTING.md.

Thanks @TrevorBurnham for submitting this PR, from your description of the error packages/@aws-cdk-testing/framework-integ && yarn integ test/aws-ecs-patterns/test/fargate/integ.queue-processing-fargate-service-grace-period.js --update-on-failed, which gave me "No such integ test". , can you see the compiled file in local with your changes.

For successfully building the integration test with latest changes from aws-cdk lib, you can run
npx lerna run build --scope=aws-cdk-lib --scope=@aws-cdk-testing/framework-integ —scope=@aws-cdk —skip-nx-cache

[TrevorBurnham]

@shikha372 Thank you! That command allowed me to run the integration test.

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

[shikha372]

LGTM! Thank you @TrevorBurnham for your contribution

[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).

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[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).

Pull request has been modified.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: be05dab
• 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).

[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.