SEC-2678 fix catalog-info.yaml validation errors#45
Open
NnnOooPppEee wants to merge 1 commit into
Open
Conversation
Author
|
Could a maintainer or code owner of this repo please review, approve, and merge this PR? It is a low-risk |
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
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
Automated cleanup of
catalog-info.yamlso the entity passes Backstage catalog validation. The same defects were repeated on every catalog refresh and dominated theservice:backstagelog volume (the "Policy check failed" family was 69% of all logs).This change does one or more of:
PLACEHOLDER-ADD-*-URL,N/A) that are not valid URLs. Real links are kept.code-lang:tags to lowercase with dashes (e.g.code-lang:TypeScripttocode-lang:typescript). Colons are preserved.No functional or ownership changes. Part of the Backstage logging cleanup tracked in SEC-2678.
Test plan
Backstage re-validates the entity on its next refresh; the repeating
Policy check failed for component:default/<name>warning for this repo should stop.