ECS wait services-stable returns prematurely when leveraging --force-new-deployment rollout

[ohshazbot]

Describe the bug

When deploying leveraging --force-new-deployment to reuse existing task definition and then attempting to use ecs wait services-stable results in the wait returning before the rollout of the new software versions completes.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

I would expect ecs wait services-stable to wait until the deployment completes (or times out) before returning

Current Behavior

ecs wait services-stable returns after a subset of instances are updated, resulting in the operation completing while a mix of old and new versions are operational

Reproduction Steps

aws ecs update-service --cluster ${ECS_CLUSTER} --service ${SERVICE_NAME} --force-new-deployment
aws ecs wait services-stable --cluster ${ECS_CLUSTER} --services ${SERVICE_NAME}

And observe (quickly) that the service is still mid-deployment

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.18.4

Environment details (OS name and version, etc.)

Python/3.12.7 Linux/6.8.0-51-generic source/x86_64.ubuntu.24