containers-roadmap
containers-roadmap copied to clipboard
aws
Overrides all of task definition parameters
Start-Task and Run-Task API can overrides the task definition.
But it supports a few parameters only. (command, environment and taskRoleArn).
I would like to overrides other parameters. (ex: hostname,logConfiguration ..)
It would be good to be able to overrides all of task definition parameters.
Same here, in our application it's the volumes:host:sourcePath that needs to be set for each individual task, and currently we have to register a new task definition just for that (all other parameters are kept the same). But there's a hard limit on task definition registration rate of 1/sec, which could be very limiting if we need to do that for thousands of tasks at a time. I imagine other applications have similar problems.
We would greatly benefit if you could override CPU and memory limits. For us, these parameters change depending on the input message. Our current workaround is to create multiple task definitions.
@egafni @billyshambrook CPU, memory, and memory reservation can now be overridden through the RunTask and StartTask API.
I'll leave this issue open as the other task definition fields are not yet supported for overrides.
Hi @samuelkarp, it would be great if we could the new Fargate task CPU and memory limits as well!
2 years have passed. only 5 parameters it's possible to override... Great progress!
stuck in aws-cli doc https://docs.aws.amazon.com/cli/latest/reference/ecs/run-task.html and finally find this thread...
Support @ppdeassis
We have one common container where the application is built, but also all scheduled tasks files are placed. The application and scheduled tasks are related, so building them and having them together in the same Docker image make sense for us.
But, we would like to override the logConfiguration option. That way we have one common task definition which is the master, but depending on which command is run inside the container, the log group name can vary. E.g. "applicationsLogs" vs. "db-table-optimize",
I'm also looking to override logConfiguration. My use case is to use the same base task definition in a multi-tenant application and replace the stream prefix for each tenant to have log streams of the form <tenant id>/<container name>/<task id>. I can generate one task definition per tenant, but it would be much easier to manage this with a handful of task definitions instead of thousands
Another use case for logConfiguration override:
We have an administrative task definition which can be run with different parameters injected into container environment (such as project_id). It would be great to be able to reflect the parameter(s) value in the log stream prefix as well, during task run. Otherwise one cannot easily identify relevant log stream for particular task run.
Overriding the container (full registry path) is critical for implementing more dynamic container references. In the case of leveraging a Fargate configuration for processing CI pipelines, the pipeline definitions allow the CI developer to specify containers from any public container registry or private elastic container registry they have access to.
Would like to be able to override image or image tag to pull from ECR. If we tag an image we need to create an new task definition afaik.
We would love to hear for logConfiguration update from you guys. eagerly waiting for it. it was raised since 2016 hope we will have this update soon.
Indeed especially for overriding the image (or at least the tag)
In the context of a CI that generates as many tags as github commits sha, if we want to test a task run for those we would then need to create as many task-definition versions...
Anyone knows a workaround applicable currently?
+1 on image override.
Is there any ETA for this? I am setting up a serverless Gitlab runner on Fargate/ECS and would be nice to have this implemented. At the moment we have to use generic images, which is fine for now as we don't have complex pipelines but we may need in future.
hard to believe this has been open since 2016 and still not implemented.
It's really important to be able to override image and other parameters.
yeah, I think AWS is probably giving up or has already given up ECS, just dont want people to rush out
