Commit 79133f8
authored
Skip redundant force-deploy when tf-apply already triggered a rollout (#52)
## Summary
When tf-apply updates the ECS service (new task def revision), ECS
already starts a rolling deployment. The ecs-deploy step was then
calling `--force-new-deployment` on top of that, causing **two
sequential deployments** and doubling the stabilization wait (~5 min
instead of ~2 min).
Now checks if a deployment is already in progress (deployment count > 1)
and skips the force if so.
## Test plan
- [ ] Merge and trigger platform-test-app
- [ ] When tf-apply runs (has changes): deploy should say "Deployment
already in progress, waiting..." and finish in ~2 min
- [ ] When tf-apply is skipped (no changes): deploy should force as
before1 parent 458e08a commit 79133f8
1 file changed
Lines changed: 17 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
7 | | - | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
8 | 10 | | |
9 | 11 | | |
10 | 12 | | |
11 | 13 | | |
12 | 14 | | |
13 | 15 | | |
14 | 16 | | |
15 | | - | |
16 | | - | |
17 | | - | |
18 | | - | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
19 | 30 | | |
20 | 31 | | |
21 | 32 | | |
| |||
0 commit comments