Hello, is there a way to launch a different task definition per repository? We are using the

ECSRunLauncher

and specifying a

task_definition

. We have repositories which define jobs that require different IAM policies (e.g each repo needs access to different AWS resources). Can we define the task_definition ARN as an environment variable on the individual repository? Then the dagit/daemon can choose which ARN to use for the pipeline.

Hi josh - this is a reasonable request, but we don't have it available yet in the EcsRunLauncher. The way I'm imagining this working with the hooks that we currently have would be to allow you to specify a task ARN as a task on a job (like the resource example here: https://docs.dagster.io/deployment/guides/aws#customizing-cpu-and-memory-in-ecs). We don't have that yet, but I do not think it would be a significant lift to add, I can file an issue for it.

Great, thanks for the quick response 😀