chore(catalog): Remove library and devtool deps from spec.dependsOn#165
Merged
Merged
Conversation
Libraries and devtools should not appear in spec.dependsOn. These dependencies are already tracked by GitHub (via repository dependencies and code ownership), so listing them in Backstage adds no value. More importantly, Backstage propagates dependsOn into Datadog Service Catalog, where these spurious edges create noise in service dependency graphs and alert routing. The dependsOn relation is intended to express runtime or deployment dependencies between entities -- not tooling or shared-library relationships. Remove all Component references of type library or devtool from spec.dependsOn in this repo's catalog-info.yaml. Where removing those entries empties the list, the dependsOn key is removed entirely. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Libraries and devtools should not appear in spec.dependsOn. These
dependencies are already tracked by GitHub (via repository
dependencies and code ownership), so listing them in Backstage adds
no value. More importantly, Backstage propagates dependsOn into
Datadog Service Catalog, where these spurious edges create noise in
service dependency graphs and alert routing.
The dependsOn relation is intended to express runtime or deployment
dependencies between entities -- not tooling or shared-library
relationships.
Remove all Component references of type library or devtool from
spec.dependsOn in this repo's catalog-info.yaml. Where removing
those entries empties the list, the dependsOn key is removed
entirely.