-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat(dependency): Adding dependency graph to start services #163
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #163 +/- ##
==========================================
+ Coverage 90.67% 90.98% +0.31%
==========================================
Files 20 20
Lines 1104 1154 +50
==========================================
+ Hits 1001 1050 +49
- Misses 103 104 +1 ☔ View full report in Codecov by Sentry. |
"grandparent-service": { | ||
"description": "grandparent-service", | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see why we have this, but aren't we planning on moving away from this pattern and toward having different naming for self-referenced containerized versions of the service?
Currently, our logic does not handle bringing up services in the correct order such that dependencies are started before their dependents. This change addresses that by constructing a dependency graph and using reverse topological ordering to determine the ordering in which we should bring services up.