Skip to main content

Backstage Software Templates

The Software Templates part of Backstage is a tool that can help you create Components inside Backstage. By default, it has the ability to load skeletons of code, template in some variables, and then publish the template to some locations like GitHub or GitLab.

Getting Started​

Be sure to have covered Getting Started with Backstage before proceeding.

Note: if you're running Backstage with Node 20 or later, you'll need to pass the flag --no-node-snapshot to Node in order to use the templates feature. One way to do this is to specify the NODE_OPTIONS environment variable before starting Backstage: export NODE_OPTIONS=--no-node-snapshot

The Software Templates are available under /create. For local development you should be able to reach them at http://localhost:3000/create.

Once there, you should see something that looks similar to this:

Create Image

Choose a template​

When you select a template that you want to create, you'll be taken to the next page which may or may not look different for each template. Each template can ask for different input variables, and they are then passed to the templater internally.

Enter some variables

After filling in these variables, you'll get some more fields to fill out which are required for Backstage usage: the owner (which is a user in the backstage system), and the storePath which is a destination URL to create for the provider, for instance https://github.com/backstage/my-new-repository, or https://gitlab.com/myorg/myrepo.

Enter Backstage vars

Run!​

Once you've entered values and confirmed, you'll then get a popup box with live progress of what is currently happening with the creation of your template.

Templating Running

It shouldn't take too long, and you'll have a success screen!

Templating Complete

If it fails, you'll be able to click on each section to get the log from the step that failed which can be helpful in debugging.

You can also cancel the running process. Once you clicked on button "Cancel", the abort signal will be sent to a task and all next steps won't be executed. The current step will be cancelled only if it supports it.

Templating failed

View Component in Catalog​

When it's been created, you'll see the View in Catalog button, which will take you to the registered component in the catalog:

Catalog

And then you'll also be able to see it in the Catalog View table:

Catalog

Disable Register Existing Component button​

There could be situations where you would like to disable the Register Existing Component button for your users. For example:

Disable Button

To do so, you will un-register / remove the catalogImportPlugin.routes.importPage from backstage/packages/app/src/App.tsx:

 const app = createApp({
   apis,
   bindRoutes({ bind }) {
-    bind(scaffolderPlugin.externalRoutes, {
-      registerComponent: catalogImportPlugin.routes.importPage,
-    });
     bind(orgPlugin.externalRoutes, {
       catalogIndex: catalogPlugin.routes.catalogIndex,
     });

After the change, you should no longer see the button.