You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
The DesiredCount property should be retrieved from current ECS Service when replacement update without desiredCount specified.
Which service(s) is this request for?
ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? issue-493
We found the optional desiredCount already released one month ago. We already tested two scenarios in above link which works well.
However, here is another situation:
An ECS service is running with desiredCount equals to 5.
Replacement update was triggered when we apply new CFN without desiredCount specified.
New ECS service was created, but the desiredCount go back to 1 automatically.
Ideally, the new ECS service should keep the same desiredCount as previous service after update.
Are you currently working around this issue?
In our case, the desiredCount is mandatory which can not be ignored. Before update, we will retrieve desiredCount from current ECS service. If we want to leverage optional desiredCount, we need to set a value for it to keep the size all the time. Which is not optional actually.
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
The DesiredCount property should be retrieved from current ECS Service when replacement update without desiredCount specified.
Which service(s) is this request for?
ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
issue-493
We found the optional desiredCount already released one month ago. We already tested two scenarios in above link which works well.
However, here is another situation:
Ideally, the new ECS service should keep the same desiredCount as previous service after update.
Are you currently working around this issue?
In our case, the desiredCount is mandatory which can not be ignored. Before update, we will retrieve desiredCount from current ECS service. If we want to leverage optional desiredCount, we need to set a value for it to keep the size all the time. Which is not optional actually.
The text was updated successfully, but these errors were encountered: