SWI-11188: fix Backstage conflicting entityRef by inlining component into catalog-info.yaml#89
Closed
jgutierrezglez wants to merge 1 commit into
Closed
SWI-11188: fix Backstage conflicting entityRef by inlining component into catalog-info.yaml#89jgutierrezglez wants to merge 1 commit into
jgutierrezglez wants to merge 1 commit into
Conversation
…flicting entityRef
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
2 participants
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.
Summary
.bandwidth/catalog-info.yaml(currentlykind: Locationpointing to./component.yaml) with the component definition inlined directly askind: Componentkind: Location→ separatecomponent.yaml) causes Backstage to produce recurring "conflicting entityRef" warnings in Datadog every 30 minutes, because the named location entity collides with the generated location that mainBranchProvider already registered for this file.bandwidth/component.yamlfile is no longer needed by Backstage after this changeTracked in SWI-11188.