We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are cases where a Backstage metadata file will fail to import because of a group or other dependency that doesn't exist.
For example, if Group:engineering doesn't exist in the Backstage instance we try to import this YAML into, the import will fail.
Group:engineering
apiVersion: backstage.io/v1alpha1 kind: Component metadata: name: sample-service-1 description: A service for testing Backstage functionality annotations: github.com/project-slug: RoadieHQ/sample-service spec: type: service owner: Group:engineering lifecycle: experimental
The validator should detect these failures as part of its standard suite of checks.
The text was updated successfully, but these errors were encountered:
https://app.shortcut.com/larder/story/5575
Sorry, something went wrong.
It should also follow the targets for kind: Location
kind: Location
No branches or pull requests
There are cases where a Backstage metadata file will fail to import because of a group or other dependency that doesn't exist.
For example, if
Group:engineering
doesn't exist in the Backstage instance we try to import this YAML into, the import will fail.The validator should detect these failures as part of its standard suite of checks.
The text was updated successfully, but these errors were encountered: