DevTools

Welcome to the DevTools plugin! This plugin helps elevate useful information about a Backstage instance through the frontend, which can be helpful for an integrator for troubleshooting, reviewing, and understanding their installation.

Features

The DevTools plugin comes with two tabs out of the box.

Info

Lists helpful information about your current running Backstage instance such as: OS, NodeJS version, Backstage version, and package versions.

Backstage Version Reporting

The Backstage Version that is reported requires backstage.json to be present at the root of the running backstage instance. You may need to modify your Dockerfile to ensure backstage.json is copied into the WORKDIR of your image.

WORKDIR /app
# This switches many Node.js dependencies to production mode.
ENV NODE_ENV production

# Then copy the rest of the backend bundle, along with any other files we might want (including backstage.json).
COPY --chown=node:node ... backstage.json ./

Config

Lists the configuration being used by your current running Backstage instance.

Note: The Config tab uses the configuration schema defined by each plugin to be able to mask secrets. It does this by checking that the visibility has been marked as secret. If this is not set then the secret will appear in clear text. To mitigate this it is highly recommended that you enable the permission framework and apply the proper permissions). If you do see secrets in clear text please contact the plugin's author to get the visibility set to secret for the applicable property.

Optional Features

The DevTools plugin can be setup with other tabs with additional helpful features.

External Dependencies

Lists the status of configured External Dependencies based on your current running Backstage instance's ability to reach them.

Catalog Unprocessed Entities

The Catalog Unprocessed Entities plugin has an optional tab that you can also be added that will show unprocessed entities:

Setup

The following sections will help you get the DevTools plugin setup and running.

Backend

You need to setup the DevTools backend plugin before you move forward with any of the following steps if you haven't already.

Frontend

To setup the DevTools frontend you'll need to do the following steps:

First we need to add the @backstage/plugin-devtools package to your frontend app:

# From your Backstage root directory
yarn --cwd packages/app add @backstage/plugin-devtools

Now open the packages/app/src/App.tsx file

Then after all the import statements add the following line:

import { DevToolsPage } from '@backstage/plugin-devtools';

In this same file just before the closing </ FlatRoutes>, this will be near the bottom of the file, add this line:
```
<Route path="/devtools" element={<DevToolsPage />} />
```
Next open the packages/app/src/components/Root/Root.tsx file
We want to add this icon import after all the existing import statements:
```
import BuildIcon from '@material-ui/icons/Build';
```

Then add this line just after the <SidebarSettings /> line:

<SidebarItem icon={BuildIcon} to="devtools" text="DevTools" />

Now run yarn dev from the root of your project and you should see the DevTools option show up just below Settings in your sidebar and clicking on it will get you to the Info tab

Customizing

The DevTools plugin has been designed so that you can customize the tabs to suite your needs. You may only want some or none of the out of the box tabs or you may want to add your own. The following sections explains how to do that (assuming you've already done the setup steps). As part of this example we'll also be showing how you can add the optional External Dependencies tab.

In the packages/app/src/components folder create a new sub-folder called devtools
Then in this new devtools folder add a file called CustomDevToolsPage.tsx

In the CustomDevToolsPage.tsx file add the following content:

import {
  ConfigContent,
  ExternalDependenciesContent,
  InfoContent,
} from '@backstage/plugin-devtools';
import { DevToolsLayout } from '@backstage/plugin-devtools';
import React from 'react';

export const DevToolsPage = () => {
  return (
    <DevToolsLayout>
      <DevToolsLayout.Route path="info" title="Info">
        <InfoContent />
      </DevToolsLayout.Route>
      <DevToolsLayout.Route path="config" title="Config">
        <ConfigContent />
      </DevToolsLayout.Route>
      <DevToolsLayout.Route
        path="external-dependencies"
        title="External Dependencies"
      >
        <ExternalDependenciesContent />
      </DevToolsLayout.Route>
    </DevToolsLayout>
  );
};

export const customDevToolsPage = <DevToolsPage />;

Now open the packages/app/src/App.tsx file and add the following import after all the existing import statements:
```
import { customDevToolsPage } from './components/devtools/CustomDevToolsPage';
```

Then we need to adjust our route as follows

-    <Route path="/devtools" element={<DevToolsPage />} />
+    <Route path="/devtools" element={<DevToolsPage />} >
+      {customDevToolsPage}
+    </Route>

Now run yarn dev from the root of your project. When you go to the DevTools you'll now see you have a third tab for External Dependencies

With this setup you can add or remove the tabs as you'd like or add your own simply by editing your CustomDevToolsPage.tsx file

Adding Tabs From Other Plugins

You can also add tabs to show content from other plugins that fit well with the other DevTools content.

Catalog Unprocessed Entities Tab

Here's how to add the Catalog Unprocessed Entities tab:

Install and setup the Catalog Unprocessed Entities plugin as per its documentation
Add the following import to your CustomDevToolsPage.tsx:

import { UnprocessedEntitiesContent } from '@backstage/plugin-catalog-unprocessed-entities';

Then add a new DevToolsLayout.Route to the end of your DevToolsLayout like this:

  <DevToolsLayout>
    <DevToolsLayout.Route path="info" title="Info">
      <InfoContent />
    </DevToolsLayout.Route>
    <DevToolsLayout.Route path="config" title="Config">
      <ConfigContent />
    </DevToolsLayout.Route>
    <DevToolsLayout.Route
      path="external-dependencies"
      title="External Dependencies"
    >
      <ExternalDependenciesContent />
    </DevToolsLayout.Route>
+   <DevToolsLayout.Route path="unprocessed-entities" title="Unprocessed Entities">
+     <UnprocessedEntitiesContent />
+   </DevToolsLayout.Route>
  </DevToolsLayout>

Now run yarn dev and navigate to the DevTools you'll see a new tab for Unprocessed Entities

Permissions

The DevTools plugin supports the permissions framework, the following sections outline how you can use them with the assumption that you have the permissions framework setup and working.

Note: These sections are intended as guidance and are completely optional. The DevTools plugin will work with the permission framework off or on without any specific policy setup.

Secure Sidebar Option

To use the permission framework to secure the DevTools sidebar option you'll want to do the following:

First we need to add the @backstage/plugin-devtools-common package to your frontend app:

# From your Backstage root directory
yarn --cwd packages/app add @backstage/plugin-devtools-common

Then open the packages/app/src/components/Root/Root.tsx file

Then add these imports after all the existing import statements:

import { devToolsAdministerPermission } from '@backstage/plugin-devtools-common';
import { RequirePermission } from '@backstage/plugin-permission-react';

Then make the following change:

-   <SidebarItem icon={BuildIcon} to="devtools" text="DevTools" />
+   <RequirePermission
+     permission={devToolsAdministerPermission}
+     errorPage={<></>}>
+     <SidebarItem icon={BuildIcon} to="devtools" text="DevTools" />
+   </RequirePermission>

Secure the DevTools Route

To use the permission framework to secure the DevTools route you'll want to do the following:

First we need to add the @backstage/plugin-devtools-common package to your frontend app (skip this step if you've already done this):
```
# From your Backstage root directory
yarn --cwd packages/app add @backstage/plugin-devtools-common
```
Then open the packages/app/src/App.tsx file

The add this import after all the existing import statements:

import { devToolsAdministerPermission } from '@backstage/plugin-devtools-common';

Then make the following change:

-   <Route path="/devtools" element={<DevToolsPage />} />
+   <Route path="/devtools"
+     element={
+     <RequirePermission permission={devToolsAdministerPermission}>
+       <DevToolsPage />
+     </RequirePermission>
+     }
+   />

Note: if you are using a customDevToolsPage as per the Customizing documentation the changes for Step 4 will be:

-   <Route path="/devtools" element={<DevToolsPage />} />
+   <Route path="/devtools"
+     element={
+     <RequirePermission permission={devToolsAdministerPermission}>
+       <DevToolsPage />
+     </RequirePermission>
+     }
+   >
+     {customDevToolsPage}
+   </Route>

Permission Policy

Here is an example permission policy that you might use to secure the DevTools plugin:

// packages/backend/src/plugins/permission.ts

class TestPermissionPolicy implements PermissionPolicy {
  async handle(request: PolicyQuery): Promise<PolicyDecision> {
    if (isPermission(request.permission, devToolsAdministerPermission)) {
      if (
        user?.identity.ownershipEntityRefs.includes(
          'group:default/backstage-admins',
        )
      ) {
        return { result: AuthorizeResult.ALLOW };
      }
      return { result: AuthorizeResult.DENY };
    }

    if (isPermission(request.permission, devToolsInfoReadPermission)) {
      if (
        user?.identity.ownershipEntityRefs.includes(
          'group:default/backstage-admins',
        )
      ) {
        return { result: AuthorizeResult.ALLOW };
      }
      return { result: AuthorizeResult.DENY };
    }

    if (isPermission(request.permission, devToolsConfigReadPermission)) {
      if (
        user?.identity.ownershipEntityRefs.includes(
          'group:default/backstage-admins',
        )
      ) {
        return { result: AuthorizeResult.ALLOW };
      }
      return { result: AuthorizeResult.DENY };
    }

    if (
      isPermission(
        request.permission,
        devToolsExternalDependenciesReadPermission,
      )
    ) {
      if (
        user?.identity.ownershipEntityRefs.includes(
          'group:default/backstage-admins',
        )
      ) {
        return { result: AuthorizeResult.ALLOW };
      }
      return { result: AuthorizeResult.DENY };
    }

    return { result: AuthorizeResult.ALLOW };
  }
}

To use this policy you'll need to make sure to add the @backstage/plugin-devtools-common package to your backend you can do that by running this command:

# From your Backstage root directory
yarn --cwd packages/backend add @backstage/plugin-devtools-common

You'll also need to add these imports:

import {
  devToolsAdministerPermission,
  devToolsConfigReadPermission,
  devToolsExternalDependenciesReadPermission,
  devToolsInfoReadPermission,
} from '@backstage/plugin-devtools-common';

Note: The group "group:default/backstage-admins" is simply an example and does not exist. You can point this to any group you have in your catalog instead.

Customizing with Permissions

If you followed the Customizing documentation and want to use permission there this is what your CustomDevToolsPage.tsx would look like:

import {
  ConfigContent,
  ExternalDependenciesContent,
  InfoContent,
} from '@backstage/plugin-devtools';
import { DevToolsLayout } from '@backstage/plugin-devtools';
import {
  devToolsConfigReadPermission,
  devToolsExternalDependenciesReadPermission,
  devToolsInfoReadPermission,
} from '@backstage/plugin-devtools-common';
import { RequirePermission } from '@backstage/plugin-permission-react';
import React from 'react';

const DevToolsPage = () => {
  return (
    <DevToolsLayout>
      <DevToolsLayout.Route path="info" title="Info">
        <RequirePermission permission={devToolsInfoReadPermission}>
          <InfoContent />
        </RequirePermission>
      </DevToolsLayout.Route>
      <DevToolsLayout.Route path="config" title="Config">
        <RequirePermission permission={devToolsConfigReadPermission}>
          <ConfigContent />
        </RequirePermission>
      </DevToolsLayout.Route>
      <DevToolsLayout.Route
        path="external-dependencies"
        title="External Dependencies"
      >
        <RequirePermission
          permission={devToolsExternalDependenciesReadPermission}
        >
          <ExternalDependenciesContent />
        </RequirePermission>
      </DevToolsLayout.Route>
    </DevToolsLayout>
  );
};

export const customDevToolsPage = <DevToolsPage />;

Configuration

The following sections outline the configuration for the DevTools plugin.

Package Dependencies

By default, only packages with names starting with @backstage and @internal will be listed on the main "Info" tab. If you would like additional packages to be listed, you can specify the package prefixes (not regular expressions) in your app-config.yaml. For example, to not only provide version information about backstage plugins provided by the core application (@backstage/* modules) but also @roadiehq and @spotify plugins, you can specify this configuration:

devTools:
  info:
    packagePrefixes:
      # Note that you MUST have quotes around these. The YAML won't be valid
      # if you don't, because of the leading at-symbols.
      - '@roadiehq/backstage-'
      - '@spotify/backstage-'

External Dependencies Configuration

If you decide to use the External Dependencies tab then you'll need to setup the configuration for it in your app-config.yaml. If there is no endpoints configured, then the tab will be empty. Here's an example:

devTools:
  externalDependencies:
    endpoints:
      - name: 'Google'
        type: 'fetch'
        target: 'https://google.ca'
      - name: 'Google Public DNS'
        type: 'ping'
        target: '8.8.8.8'

Configuration details:

endpoints is an array
name is the friendly name for your endpoint
type can be either ping or fetch and will perform the respective action on the target
target is either a URL or server that you want to trigger a type action on

External Dependencies Requirements

If you are using the ping type you must ensure that ping is available in the Host OS that is running Backstage. For example you may need to add ping into the Dockerfile that builds your Backstage image:

RUN --mount=type=cache,target=/var/cache/apt,sharing=locked \
    --mount=type=cache,target=/var/lib/apt,sharing=locked \
    apt-get update && \
    apt-get install -y  ... iputils-ping

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

DevTools

Features

Info

Backstage Version Reporting

Config

Optional Features

External Dependencies

Catalog Unprocessed Entities

Setup

Backend

Frontend

Customizing

Adding Tabs From Other Plugins

Catalog Unprocessed Entities Tab

Permissions

Secure Sidebar Option

Secure the DevTools Route

Permission Policy

Customizing with Permissions

Configuration

Package Dependencies

External Dependencies Configuration

External Dependencies Requirements

Files

README.md

Latest commit

History

README.md

File metadata and controls

DevTools

Features

Info

Backstage Version Reporting

Config

Optional Features

External Dependencies

Catalog Unprocessed Entities

Setup

Backend

Frontend

Customizing

Adding Tabs From Other Plugins

Catalog Unprocessed Entities Tab

Permissions

Secure Sidebar Option

Secure the DevTools Route

Permission Policy

Customizing with Permissions

Configuration

Package Dependencies

External Dependencies Configuration

External Dependencies Requirements