ref(dependency-graph): Adding more context to the dependency graph #248
+437
−60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds context about whether a given node in the dependency graph is a docker compose service (leaf) or a devservices service. This enables us to avoid cycles when we have docker compose services with the same name as the devservices service which is a common thing we see such as with snuba and it's container.
https://linear.app/getsentry/issue/DI-661/add-more-context-to-dependency-graph
This is required to enable the improvements we are looking to make to the status command: https://linear.app/getsentry/issue/DI-647/rework-status-command.