initial commit

Change-Id: I80adb770c7d485cdc89c6871a5436866722fb7dd
This commit is contained in:
Scaffolder
2026-08-10 08:25:31 +00:00
commit 35c67a8a52
139 changed files with 28500 additions and 0 deletions

65
catalog-info.yaml Normal file
View File

@@ -0,0 +1,65 @@
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: pclinic-andrej-demo1
description: 'pclinic-andrej-demo1 — renovated onto the crucible platform orchestrator'
annotations:
gitea.kyndemo.live/project-slug: validate/pclinic-andrej-demo1
gitea.kyndemo.live/repo-slug: validate/pclinic-andrej-demo1
# The orchestrator names each environment's namespace ns-xxxxx at deploy time, so a
# namespace can never be known here -- pinning one only hides the workload. Omitted
# deliberately: the Kubernetes plugin then searches every namespace it is given.
#
# kubernetes-id matches the label the score-workload module propagates from the Score
# metadata.labels block. The previous selector, app.humanitec.io/name=..., was a
# Humanitec SaaS label that nothing on this platform has ever set.
backstage.io/kubernetes-id: pclinic-andrej-demo1
backstage.io/techdocs-ref: dir:.
# Vestigial key names, live values. These drive the Orchestrator tab, which reads
# humanitec.dev/orgId and humanitec.dev/projectId; renaming the keys would break every
# entity already in the catalog, so the names stay and the values point at crucible.
humanitec.dev/orgId: crucible
# THE PROJECT IS THE APPLICATION. This was `apps-cluster`, a single project shared by
# every renovated app, which is why the Orchestrator tab on any one component listed the
# whole estate -- the tab shows a project's environments, and every app's environment
# lived in that one project. Now each app owns a project, so the tab shows this app's
# stages and nothing else. The deploy workflow creates the project, its runner rule and
# its environments on first deploy.
humanitec.dev/projectId: pclinic-andrej-demo1
# The environments are now STAGES of this application -- dev, staging, prod -- rather
# than one environment named after the component.
humanitec.dev/appId: pclinic-andrej-demo1
cjot.io/target-domain: apps
sonarqube.org/project-key: pclinic-andrej-demo1
grafana/grafana-instance: "default"
grafana/alert-label-selector: "app=pclinic-andrej-demo1"
grafana/dashboard-selector: "uid == 'otel-app-observability-v2'"
grafana.com/dashboard-url: "https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-app=pclinic-andrej-demo1"
tags:
- platform-orchestrator
- renovation
links:
# console.humanitec.dev is the dead SaaS. This is the live crucible console, deep-linked
# to the per-application environment the deploy workflow creates.
- url: https://console.dev.orchestrator.crucible.kyndemo.live/orgs/crucible/projects/pclinic-andrej-demo1/environments/dev
title: Orchestrator Console
icon: dashboard
- url: https://pclinic-andrej-demo1.apps.dev.crucible.kyndemo.live
title: Live Application
icon: web
- url: https://gitea.kyndemo.live/validate/pclinic-andrej-demo1
title: Source Repository
icon: github
- url: https://gitea.kyndemo.live/validate/pclinic-andrej-demo1/actions
title: CI/CD Pipelines
icon: code
- url: https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-app=pclinic-andrej-demo1
title: Grafana Dashboard
icon: dashboard
spec:
type: service
lifecycle: experimental
owner: platform-engineering
dependsOn:
- resource:default/cjot-aks