1. Introduction
    2. Software Catalog basics
    3. Removing the example entities
    4. Creating a software component
    5. Registering a component
    6. Moving towards a production instance
    1. Creating new components using Backstage
    2. Anatomy of a Software Template
    3. Writing new Software Templates
    4. Scaffolder actions
    5. Software Templates at Spotify
    1. Knowledge check

Onboarding Software to Backstage

45 MINS

Creating a software component

Let’s add an entity of your own to the catalog; preferably an existing service owned by your team.

  1. In the code repository for the service, create a new file catalog-info.yaml at the repository’s root.

  2. Paste the following contents:

apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  name: replace-me
  description: Replace me with a real description.
  tags:
    - go
    - website
spec:
  type: service
  lifecycle: production
  owner: your-team
  1. Update metadata.name - with a version of your service’s name that only includes lowercase, alpha-numeric characters and dashes

  2. Update metadata.description - a human-readable description of your service

  3. Update spec.owner - with your team’s name

💡 If your company already has metadata files in a different format, you can write a catalog processor to ingest those and translate to Backstage’s entity format.

  1. Commit and push this file up to your version control system and ensure it’s available in the default branch (e.g. main or master).

  2. Navigate to this catalog-info.yaml file in the web interface of your VCS and copy the URL. e.g. https://github.com/backstage/backstage/blob/master/catalog-info.yaml