I have a few services (containers) that get deployed to fargate. The problem is that the new service B requires the new service A to be up and running… as it the case, service B beats out service A by a handful of minutes , which means the site is offline/impaired.
Is there a way I can put a script, a check, something in the deploy job of service A that won’t finish the job until the service goes green? (aka online, up and running)? Or maybe make service B have a check that wont start until service A is up and running?
Or maybe there is just a workflow dependency that can be configured across workflows? What solutions have you guys come up with?
Thanks in advance for any tips !