fix(deploy): use same task definition for API and SDK services #6495
+8
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature!Changes
Fix bug where API and SDK ECS services were using different task definition revisions.
Problem: The
amazon-ecs-deploy-task-definitionaction registers a new task definition revision each time it's called. When called twice (once for API, once for SDK), the SDK service ended up with revision N+1 while API had revision N.Solution:
aws ecs update-servicefor the SDK service with the same ARN instead of calling the deploy action againNow both services use the exact same task definition revision.
How did you test this code?