Skip to content
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.

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

Handle circuit breaker rollbacks #136

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

LouisBoudreau
Copy link
Member

@LouisBoudreau LouisBoudreau commented Jan 4, 2024

Goal

The goal of this PR is to handle ECS circuit breaker rollbacks

The ECS circuit breaker rollback to a previous task definition revision. When this happens, we want our action to fail in order to alert us

En activant ce feature, nous pouvons retirer l'étape de rollback dans le CI/CD

Copy link
Collaborator

@Claude-GP Claude-GP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job, c'est nice comme mécanisme et ça va simplifier les autres workflows!

core.info(`A new PRIMARY deployment is registered with task definition ${primaryDeployment.taskDefinitionArn}.`);
return DeploymentOutcome.SKIPPED;
} else if (isServiceStable(clusterName, serviceName)) {
} else if (primaryDeployment.taskDefinitionArn !== taskDefinitionArn && newTaskDefinitionRevision < previousTaskDefinitionRevision) {
core.error(`A rollback has been triggered. Starting a new deployment with task definition ${primaryDeployment.taskDefinitionArn}.`);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Juste pour bien comprendre circuit breaker, quand un rollback est trigger, il rollback au dernier déploiement COMPLETED et ne redéploie pas de container?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

il rollback au dernier déploiement COMPLETED
Oui exact

et ne redéploie pas de container?

Ca dépend, si pour une raison X, disons 25% containers avaient réussit à tombé healthy. Alors lors du rollback il va devoir redéployé certains containers pour honorer les desired count du service

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants