This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
feat: add backstage rule for catalog-info validation #104
Conversation
This file contains 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
raphapr
force-pushed
the
feat/backstage-rule
branch
from
471bbc8 to
53e5910
Compare
raphapr
changed the title
raphapr
force-pushed
the
feat/backstage-rule
branch
from
53e5910 to
775dbbd
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation and context for the change
(WIP) Peril doesn't validate
catalog-info.yamlcatalog file for BackstageA clear description of the change
Add a danger rule that validates the
catalog-info,yamlfile and fails whether it is not found or valid. The validation uses a specific schema for Loadsmart.Testing
Testing instructions
CI covers it
Rollback
Rollback instructions
Revert this PR should be enough