Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add catalog-info.yaml config file #2341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Closed
Manojk-11 wants to merge 1 commit into from
+10 −0
Closed

Add catalog-info.yaml config file #2341

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions catalog-info.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: full-stack-fastapi-template
annotations:
github.com/project-slug: Manojk-11/full-stack-fastapi-template
spec:
type: other
lifecycle: unknown
owner: Backstage Users

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a Backstage entity ref for the owner

Backstage parses spec.owner as an entity reference, not a display label; the referenced entity name follows the catalog name rules, whose defaults disallow spaces. In a standard Backstage catalog this value will not match a registerable Group/User owner, so the component ends up with an unusable ownership relation. Use the catalog entity ref/slug instead, e.g. group:default/backstage-users.

Useful? React with 👍 / 👎.

Loading