Skip to content

Skip redundant force-deploy when tf-apply already triggered a rollout #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Alexanderamiri merged 1 commit into from
Mar 12, 2026
Merged

Skip redundant force-deploy when tf-apply already triggered a rollout #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 17 additions & 6 deletions scripts/ecs-deploy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,19 +3,30 @@
#
# Forces a new deployment so ECS pulls the latest image for the current
# task definition. Does NOT create new task definition revisions — that's
# Terraform's job. This avoids drift between TF-managed task defs
# (with security hardening, volumes, etc.) and deploy-time revisions.
# Terraform's job.
#
# If a deployment is already in progress (e.g. from tf-apply), skips the
# force and just waits for it to stabilize.
#
# Usage: ecs-deploy.sh
#
# Env: CLUSTER, SERVICE

set -e

echo "Forcing new deployment for ${SERVICE} on ${CLUSTER}..."
aws ecs update-service \
--cluster "$CLUSTER" --service "$SERVICE" \
--force-new-deployment > /dev/null
# Check if a deployment is already rolling out
DEPLOYMENT_COUNT=$(aws ecs describe-services \
--cluster "$CLUSTER" --services "$SERVICE" \
--query 'length(services[0].deployments)' --output text)

if [ "$DEPLOYMENT_COUNT" -gt 1 ]; then
echo "Deployment already in progress (${DEPLOYMENT_COUNT} deployments), waiting..."
else
echo "Forcing new deployment for ${SERVICE} on ${CLUSTER}..."
aws ecs update-service \
--cluster "$CLUSTER" --service "$SERVICE" \
--force-new-deployment > /dev/null
fi

echo "Waiting for service to stabilize..."
aws ecs wait services-stable --cluster "$CLUSTER" --services "$SERVICE"
Expand Down