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
These options are pretty much important to control deployment flow and make sure that certain number of containers are serving traffic during deployment of new version. AWS makes it possible to set these values either during ecs service creation or during its update (e.g. when new revision of task definition is specified for service).
Thank you!
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 28, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Looks like terraform aws_ecs_service resource doesn't support min and max healthy percent:
http://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service.html
https://www.terraform.io/docs/providers/aws/r/ecs_service.html
These options are pretty much important to control deployment flow and make sure that certain number of containers are serving traffic during deployment of new version. AWS makes it possible to set these values either during ecs service creation or during its update (e.g. when new revision of task definition is specified for service).
Thank you!
The text was updated successfully, but these errors were encountered: