https://dagster.io/ logo
Powered by
#ask-community
Title
# ask-community
m

Mike Atlas

08/29/2022, 9:55 PM
hey dagster friends, could someone help me understand if it's possible for the 
EcsRunLauncher
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.
🤖 1
Alternatively, 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
really though the important part for me is that I'd like to keep 
taskRoleArn
separately assigned for the user code and daemon tasks
should i actually just be specifying 
taskRoleArn
somewhere else? I see it's in 
metadata
so maybe I can just put the ARN in my user code?
maybe i can set it via 
ecs/task_overrides
?
@ramshackle-jamathon saw you had recently committed some code around 
ecs/task_overrides
maybe you have another example?
Copy code
@job(
   tags = {
    "ecs/task_overrides": {
        "taskRoleArn": "goes-here",
   }
  }
)
maybe?
btw this works! but i had to upgrade my dagster first to get the latest
Copy code
tags = {
    "ecs/task_overrides": {
        "taskRoleArn": "goes-here",
   }
  }
dagster bot responded by community 1
Powered by