Mike Atlas
08/29/2022, 9:55 PMEcsRunLauncher
task definition to use the user-code task definition to inherit-from (this changes each new deployment) rather than the daemon's task?
in the docs, https://docs.dagster.io/deployment/guides/aws#launching-runs-in-ecs there's an example for run_launcher
config to specify a task_definition
ARN, but this value has to be set in the daemon configuration file.Mike Atlas
08/29/2022, 9:57 PMAlternatively, you can define your own task definition in your dagster.yaml:This ^ refers to the daemon config. And the code that loads the "self" task def from the daemon is https://github.com/dagster-io/dagster/blob/1.0.6/python_modules/libraries/dagster-aws/dagster_aws/ecs/launcher.py#L336
Mike Atlas
08/29/2022, 9:58 PMtaskRoleArn
separately assigned for the user code and daemon tasksMike Atlas
08/29/2022, 10:00 PMtaskRoleArn
somewhere else? I see it's in metadata
so maybe I can just put the ARN in my user code?Mike Atlas
08/29/2022, 10:18 PMecs/task_overrides
?Mike Atlas
08/29/2022, 10:20 PMecs/task_overrides
maybe you have another example?Mike Atlas
08/29/2022, 10:23 PM@job(
tags = {
"ecs/task_overrides": {
"taskRoleArn": "goes-here",
}
}
)
maybe?Mike Atlas
08/30/2022, 1:57 PMtags = {
"ecs/task_overrides": {
"taskRoleArn": "goes-here",
}
}