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

Support for ECS service deploymentConfiguration #4456

Closed
brentonannan opened this issue Dec 29, 2015 · 12 comments
Closed

Support for ECS service deploymentConfiguration #4456

brentonannan opened this issue Dec 29, 2015 · 12 comments

Comments

@brentonannan
Copy link

Are there plans to support deploymentConfiguration for ECS service definitions as described on the documentation, and supported on the ECS console?

@maheshpec
Copy link

+1

@aldarund
Copy link

+1. Need this :( Any chances it will be done soon?

@anosulchik
Copy link

+1

2 similar comments
@nhuray
Copy link

nhuray commented Feb 2, 2016

+1

@maescomua
Copy link

+1

@benzimmer
Copy link

I think this is pretty essential because currently it takes down the whole service when doing a terraform apply. Defining the options in deploymentConfiguration would allow to do rolling restarts without downtime of the service.

@anosulchik
Copy link

@benzimmer Just a quick observation: it's still possible to change minimumHealthyPercent and maximumPercent for ECS service in AWS console to prevent downtimes, "terraform apply" won't reset those settings.

@benzimmer
Copy link

@anosulchik Nice, thanks for the hint!

I was thinking about using null_resource together with the local-exec provisioner to have a script update the settings after creation of the service.

@dquiles-handy
Copy link

👍

@stack72
Copy link
Contributor

stack72 commented Feb 21, 2016

Resolved in #5220

@stack72 stack72 closed this as completed Feb 21, 2016
@brentonannan
Copy link
Author

👍 thanks!
On 22 Feb 2016 9:36 am, "Paul Stack" notifications@github.com wrote:

Closed #4456 #4456.


Reply to this email directly or view it on GitHub
#4456 (comment).

@ghost
Copy link

ghost commented Apr 28, 2020

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 ghost locked and limited conversation to collaborators Apr 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants