-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mapping for depends_on and ContainerDependency #897
Comments
I like this idea; depends_on could be mapped to a container dependency with condition |
+1, I would find this incredibly useful! |
Where should i mention the depends_on option. In doker-compose.yml or ecs-parms.yml? Also please let me know the format as well. I want my web app should be started before my nginx server starts. |
Where should i mention the depends_on option. In doker-compose.yml or ecs-parms.yml? Also please let me know the format as well. I want my web app should be started before my nginx server starts. |
Is there any way to set of the |
Any updates on this? I would really love to have this feature. |
When this issue will be supported? |
I think customers will have to do this without the ecs-cli team. They wrote yesterday, "We’ve shifted our resources over the past few months to developing [ecs-cli] v2..." With that in mind, I suggest someone take on this code fix themselves. Fork the repo and submit a PR. We can share the PR in our private forks of this repo until/if ecs-cli team integrates the PR. |
Closing, as this feature is now available in v1.21.0 ! |
Support transformation of depends_on in Docker Compose to ContainerDependency objects in the ECS task definition.
ECS has recently announced support for container dependency within a task. When using the ecs-cli to transform a docker-compose file to an ECS task definition the options depends_on are skipped with the error:
Steps to Replicate
I. Docker-Compose File
II. Run
ecs-cli
The text was updated successfully, but these errors were encountered: