Earlier, I was having trouble running an ecs agent...
# ask-community
h
Earlier, I was having trouble running an ecs agent and was advised to invoke the command
prefect agent ecs start
with the parameter
--run-task-kwargs config.yaml
where config.yaml contains the following:
Copy code
networkConfiguration:
  awsvpcConfiguration:
    subnets:
      - 'subnet-something'
    assignPublicIp: 'ENABLED'
I would instead like to be able to input this as a command-line argument. Will there be any fixes down the road?
k
Hey, you can input it in code if you want. Do you want to see that? Do you mean you want to input
networkConfiguration
through the
prefect agent ecs start
?
h
yes. I had some issues before with this same solution, so some exact code would be great to compare. Was running into a
Failed to infer default networkConfiguration, please explicitly configure using --run-task-kwargs
error (despite passing in the networkConfiguration as a parameter)
@Kevin Kho any update on this? thanks
k
Sorry about that. Do you have any
networkConfiguration
you are using? Like are you using specific subnets for ECS?
h
yup, I am inserting my subnet into the config.yaml file as above
k
Ok got it. I know exactly what you’re saying now. You just`networkConfiguration` exposed in the CLI. I can open the feature request on the repo if you like, or you could do it if you want. Which do you prefer?
h
Yes, exactly. Could you do so? Thanks! It would just simpler for us rather than having to store a bunch of s3 files with specific subnets for separate use cases
k
Yep I’ll take care of making the issue!
🙌 1
You can chime in here if it needs more detail I honestly don’t know when we’ll get to it though as this issue has workarounds and we haven’t gotten this request before. I’ll be sure to make other people interested chime in there when I see this feature request raised by other community members.
h
I see. thanks for the help anyways!
k
Hey sorry to say but this feature request was rejected because it opens the door of exposing every available configuration of ECS on the agent, and it was deemed that the task definition is the appropriate place to do this. The effort will instead be around thinking how make the task definition easier to use.
h
yeah, i saw. that would also be helpful as well, i think