Page MenuHomeElementl

Configure task_definition and container_name

Authored by jordansanders on Jun 30 2021, 8:48 PM.
Referenced Files
F2763691: D8642.diff
Sun, Jan 29, 5:18 AM
Unknown Object (File)
Sat, Jan 21, 2:40 PM
Unknown Object (File)
Fri, Jan 6, 4:14 AM
Unknown Object (File)
Dec 25 2022, 7:08 PM
Unknown Object (File)
Dec 21 2022, 4:39 AM
Unknown Object (File)
Dec 19 2022, 7:21 AM
Unknown Object (File)
Dec 12 2022, 2:43 AM
Unknown Object (File)
Dec 3 2022, 10:36 PM



Previously, the EcsRunLauncher always created a new task definition.

Now, you can provide a task definition (family or ARN). If configured,
the EcsRunLauncher won't create its own task definition. This is a
coarse grained way of controlling how your runs execute. For example, if
you don't want to inheret the same memory specifications of the
parent process when running your pipeline, then you can define a new
task definition with different memory.

The EcsRunLauncher does minimal checks to ensure a task can actually be
placed using the custom task definition. It checks only that the task
definition actually exists and that there's a container that can be
overridden to execute teh dagster api execute_run command. By default,
it expects a container named "run" to be defined, but you can optionally
configure your own container name as well.

Depends on D8641

Test Plan


Diff Detail

R1 dagster
Lint Passed
No Test Coverage