Paths/DevOps Engineer/Platform Engineering / Service Catalog
Register a Service in the Catalog
Backstage-style catalogs read a catalog-info.yaml from each repository. Write one for the service you templated — ownership, domain and component type.
Validator
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/templates/service-template/catalog-info.yaml exists○
- It declares a Component owned by a team○
02Walkthrough
4 steps- 01
Create the template repository
Every lab starts from a fresh shell — scaffolding first, then the descriptor.
mkdir -p ~/templates/service-template - 02
Enter the template repository
The catalog file lives at the repo root, next to the code.
cd ~/templates/service-template - 03
Write the catalog descriptor
apiVersion and kind: Component identify it as a service; metadata gives it a name; spec.owner points at a catalog group — the team paged when it breaks.
echo 'apiVersion: backstage.io/v1alpha1\nkind: Component\nmetadata:\n name: service-template\nspec:\n type: service\n owner: platform-team' > catalog-info.yaml - 04
Review and submit
cat the file. Every service in the company gets one of these — together they form the catalog.
cat catalog-info.yaml
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list