-
Notifications
You must be signed in to change notification settings - Fork 422
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
Dependency ordering being ignored #2723
Comments
Hello @bpottier. It seems like the manifest is not configured properly. Could you refer to this example? |
Hi @bpottier 👋 Is it possible to modify the manifest like this to see if the dependency works? image:
depends_on:
content: HEALTHY Thanks! |
Sorry about the delay. My manifest was incorrect. I also realized health checks are not supported on sidecars so what I'm trying to accomplish is not possible. Is there already an issue for adding health checks to sidecars? |
No worries! thanks for getting back to us :D
Oh noo you're right the field is not supported at the moment. It should be a small issue for us to fix, would you mind creating the issue for us and we can prioritize it the upcoming sprint (on Monday)? |
Will do! |
This is now released in https://github.com/aws/copilot-cli/releases/tag/v1.11.0! 🎉 |
I'm using version 1.9.0 and am trying to have a dependency condition of "HEALTHY" for my main container on a sidecar container (for a scheduled job). The task definition being generated doesn't include any dependency ordering. Is there something I'm missing?
mainfiest for main container:
The text was updated successfully, but these errors were encountered: