From f0475ac198b8c7613a7177812d43c0d3ddff3bd1 Mon Sep 17 00:00:00 2001 From: Evan Vetere Date: Sat, 12 Sep 2026 13:32:01 -0400 Subject: [PATCH] fix: replace scaffold owner in root catalog-info The scaffold catalog-info.yaml this repository ships at its root still declared owner john@example.com, lifecycle experimental, and a description calling this an example Backstage application. The running catalog ingests every repository in the org at this path, so it reads two Component entities named backstage: the curated one from datum-cloud/infra and this one carrying placeholder scaffold text. Set the owner to ecv@datum.net. Also correct lifecycle to production and the description to reflect what this repository actually is, since both were plainly false for a service running in production today. Left spec.type as website; the org-model Component in infra classifies this app as a service, but this file predates that model and nothing here confirms one classification is wrong. Claude-Session: https://claude.ai/code/session_01QV419URMnKWckY8s6j4Dwi --- catalog-info.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/catalog-info.yaml b/catalog-info.yaml index adbb41d..8fc2209 100644 --- a/catalog-info.yaml +++ b/catalog-info.yaml @@ -2,12 +2,12 @@ apiVersion: backstage.io/v1alpha1 kind: Component metadata: name: backstage - description: An example of a Backstage application. + description: Datum's Backstage developer portal and software catalog. # Example for optional annotations # annotations: # github.com/project-slug: backstage/backstage # backstage.io/techdocs-ref: dir:. spec: type: website - owner: john@example.com - lifecycle: experimental + owner: ecv@datum.net + lifecycle: production