Support ECS specific fields that are not supported in compose

[yinshiua]

ecs-cli compose does not support ECS specific parameters that are in compose including essential, Task role ARN, Network mode, etc.

[yinshiua]

Related to #153

[jonydev]

hi, @yinshiua. Is there any plan to provide the function of Network mode? We have a very strong demand on that.

[yinshiua]

@jonydev Yes, we are planning on adding Network Mode into the CLI. We are working on putting together a proposal.

[qmcree]

+1... having the ability to mark containers as non-essential is really needed. Currently, the alternative of manually creating new task definitions is quite clunky.

[esetnik]

I second what @qmcree said. It's absolutely critical to be able to mark one-off task containers as non-essential.

[rbalicki2]

@qmcree could you go into more detail about your workaround? I'm new to using ecs-cli and am a bit confused.

[qmcree]

@rbalicki2 My solution is less than ideal. I used the ECS CLI to parse the Docker Compose YML as best it could to get the task definitions into ECS. Then, I manually configured the non-essential containers (like a worker we have) in the AWS console. For deployments, I fabfuel/ecs-deploy via Jenkins, which will parse a task definition in JSON, but will only change the Docker image tag. If we need to make changes to anything else in the definition like add/remove environment variables, we make them directly in the console. I look forward to when we can fully leverage Compose YML's via ECS CLI to make these changes.

[rbalicki2]

@qmcree Oh ok. So right now I have

/cargo/bin/diesel migration run

# https://github.com/aws/amazon-ecs-cli/issues/267
while true
do
  sleep 100000
done

I think that'll do until this is solved from the ecs-cli end...!

[qmcree]

Hahaha, right?