What does --force-new-deployment option do? about ecspresso

[psyhomb]

@fujiwara thanks for the quick answer I will try it out this and let you know if it works!

[psyhomb]

Ok according to AWS Go SDK documentation it's not related to LB draining, it's just going to force a new deployment even if there is no service definition changes.

https://docs.aws.amazon.com/sdk-for-go/api/service/ecs/#ECS.UpdateServiceWithContext

// Whether to force a new deployment of the service. Deployments are not forced
// by default. You can use this option to trigger a new deployment with no service
// definition changes. For example, you can update a service's tasks to use
// a newer Docker image with the same image/tag combination (my_image:latest)
// or to roll Fargate tasks onto a newer platform version.

So my question is, is there is a way to force stop of ECS tasks (running:0) w/ this tool, w/o need to wait for LB draining to be completed successfully. This is something I would like to implement for dev and test environments.

Thanks

[fujiwara]

--force-new-deployment only works with --skip-task-definition actually.
If you want to replace all tasks in service without update task definition, use --skip-task-definition and --force-new-deployment both.
When a task definition in service is unchanged, ECS does not replace tasks in the service by default.

So my question is, is there is a way to force stop of ECS tasks (running:0) w/ this tool, w/o need to wait for LB draining to be completed successfully. This is something I would like to implement for dev and test environments.

--tasks option is for that use case. e.g.ecspresso deploy --skip-task-definiton --tasks 0