ecs-run-task

ecs-run-task copied to clipboard

Execution doesn't terminate even after all tasks have stopped and logs have been received

5

Thanks for such an useful utility. It works wonderfully but in a Centos container, the binary doesn't terminate even after all tasks have stopped and logs have been received. go...

jpadhye

Adding `--platform-version` parameter to pass the Fargate platform version to RunTask. This allows to run a Fargate task on platform version `1.4.0` which is still not `LATEST`

ckornacker

missing family field in task definition field causes a nil pointer derefence panic when logging we can use a value here instead of a pointer and now get a debug...

KlotzAndrew

I see there is a branch called `handle-nil-reason`. I handled it a little differently, but looking at that previously made branch, maybe there should be a separate `writeTaskFinishedMessage` message that...

sherzberg

Containers that fail with no reason causes a panic

10

See https://github.com/buildkite/ecs-run-task/issues/25#issuecomment-551333825 for more background. ```go panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x895b85] goroutine 1 [running]: github.com/buildkite/ecs-run-task/runner.writeContainerFinishedMessage(0xb226e0, 0xc00009c010, 0xc0002161c0, 0xc0001bd9e0,...

sherzberg

Periodic ResourceNotReady: exceeded wait attempts errors

4

For some reason, one of our environments seems to take a little longer than average to spin up the ECS Task and associated infra. Because of this, `ecs-run-task` exits with...

jroblak

Request: re-use latest task definition if not changed

1

We run this tool as a part of a daily batch process (and it's great). However - task definitions are created for each run, and that's not ideal. Could we...

Eli-Goldberg