Adding Release Plugin to Your Backstage IDP

Before You Begin

Ensure that you have installed the Backstage application. If not, you can follow the Getting Started guide on Backstage to create one. Once you have the Backstage application installed, you can proceed with installing the plugins.

Installing and Configuring the Frontend Plugin

The frontend plugin needs to be added to your application. To do so:

1. Run the following command from the Backstage root directory:

yarn --cwd packages/app add @digital-ai/plugin-dai-release

2. Add the DaiReleasePage extension to your App.tsx.

Modify your app routes in App.tsx to include the ReleaseHomePage component exported from the plugin. For example,

// In packages/app/src/App.tsx
import {DaiReleasePage} from '@digital-ai/plugin-dai-release';
const routes = (
     <FlatRoutes>
        {/* ...other routes */}
        <Route path="/dai-release" element={<DaiReleasePage/>}/>

3. Add Digital.ai Release to your app sidebar.

// In packages/app/src/components/Root/Root.tsx
// ...
+ import {ReleaseSvgIcon} from '@digital-ai/plugin-dai-release'
// ...

// ...
// Add it under a SidebarGroup. Eg
export const Root =
   // ...
   <SidebarScrollWrapper>
       <SidebarItem icon={MapIcon} to="tech-radar" text="Tech Radar" />
+      <SidebarItem icon={ReleaseSvgIcon} to="dai-release" text="digital.ai release" />
       // ...

Installing and Configuring the Backend Plugin - Legacy Backend System

important

If you're using new Backstage backend system, refer to [Backstage New Backend System].

1. Run the following command from the Backstage root directory.

yarn --cwd packages/backend add @digital-ai/plugin-dai-release-backend

2. Create a plugin file for deploy backend in the packages/backend/src/plugins/ directory.

// packages/backend/src/plugins/dai-release.ts
import { createRouter } from '@digital-ai/plugin-dai-release-backend';
import { Router } from 'express';
import type { PluginEnvironment } from '../types';
export default function createPlugin(
  env: PluginEnvironment,
): Promise<Router> {
  return createRouter({
        logger: env.logger,
    config: env.config,
    permissions: env.permissions
  });
}

3. Modify your backend router to expose the APIs for Release backend.

// packages/backend/src/index.ts
import daiRelease from './plugins/dai-release';
// ...
async function main() 
  // ...
  // Add this line under the other lines that follow the useHotMemoize pattern
  const daiReleaseEnv = useHotMemoize(module, () => createEnv('dai-release'));
  // ...
  // Insert this line under the other lines that add their routers to apiRouter in the same way
  apiRouter.use('/dai-release', await daiRelease(daiReleaseEnv));

4. Configure the Release instance by adding the following to your app-config.yaml files.

tip

Release plugin supports multi instance integration option. All values are mandatory, and if any of the keys or values are missing, the application fails to start.

For single instance setup:

daiRelease:
   instances:
      - name: {name-of-first-instance} #
        host: {host-of-first-instance} #http://digital-ai-1.release.com:4516
        token: {token-of-first-instance}

For multi instance setup:

daiRelease:
   instances:
      - name: {name-of-first-instance} #
        host: {host-of-first-instance} #http://digital-ai-1.release.com:4516
        token: {token-of-first-instance}
      - name: {name-of-second-instance}
        host: {host-of-second-instance} #http://digital-ai-2.release.com:4516
        token: {token-of-second-instance}

Configuration Details:

• name: is used to display in UI for choosing instance.
• host: is your release application host.
• token: You must set an environment variable for your release application's API token. Create an account with read permissions and use the token from that account.

Installing and Configuring the Backend Plugin - New Backend System

The Dai Release backend plugin has support for the new backend system. To add the new backend system:

1. Run the following command from the Backstage root directory:

yarn --cwd packages/backend add @digital-ai/plugin-dai-release-backend

2. In your packages/backend/src/index.ts make the following changes:

import { createBackend } from '@backstage/backend-defaults';

  const backend = createBackend();

  // ... other feature additions

+ backend.add(import('@digital-ai/plugin-dai-release-backend'));

  backend.start();

3. Configure the Release instance by adding the following to your app-config.yaml files.

tip

Release plugin supports multi instance integration option. All values are mandatory, and if any of the keys or values are missing, the application fails to start.

For single instance setup:

daiRelease:
   instances:
      - name: {name-of-first-instance} #
        host: {host-of-first-instance} #http://digital-ai-1.release.com:4516
        token: {token-of-first-instance}

For multi instance setup:

daiRelease:
   instances:
      - name: {name-of-first-instance} #
        host: {host-of-first-instance} #http://digital-ai-1.release.com:4516
        token: {token-of-first-instance}
      - name: {name-of-second-instance}
        host: {host-of-second-instance} #http://digital-ai-2.release.com:4516
        token: {token-of-second-instance}

Configuration Details:

• name: is used to display in UI for choosing instance.
• host: is your release application host.
• token: You must set an environment variable for your release application's API token. Create an account with read permissions and use the token from that account.

Creating Users in Release

Before you can use the Release plugin for Backstage, certain prerequisites needs to be met within the Digital.ai Release. These involve creating a new API access token. For example,

1. Login as admin or user and create an access token with “Audit data” permission.

2. Alternatively, you can create a new user in Digital.ai Release for Backstage. For example, ‘backstage-user’.

3. Create a new role “backstage-role” and add principal “backstage-user”.

4. Assign “Audit data” permission to “backstage-role”.

5. Login as “backstage-user” and create an ccess token with all permissions.

Using the Release Plugin in Backstage

1. Open your Backstage application and from the sidebar, click Digital.ai release. The Release plugin dashboard appears.

You can view active release details such as release Title, Folder, Status, and Start Date.

2. Under Title, click the link to view the release flow.

note

The latest release appears on top.

3. From Choose Instance dropdown, select the instance required.

4. Click the filter icon. This opens the Filters dialog,initially empty.

As needed, you can filter based on Release Status, and Start Date, From, and To. The dashboard displays the active release details for your selected filter.

5. You can use the pagination option at the bottom to navigate through the multiple pages of active releases.

Sample Deployment to View Release FLow in Backsatge

The following example shows the release flow in Backstage.

1. Log in to Release, and go to Releases. You can view the current status of all the releases.

2. To create a new release, click New Release. The Create new release dialog appears.

3. Provide the required details and click Create. The new release flow is initiated with the status Planned.

4. Next, log in to Backstage to view the active releases. You will see the new release flow listed with the status Planned.

4. To start the release flow, Click Start release in Release portal. The status of release flow changes to In progress.

5. Refresh the active releases page in Backstage. The status is updated to In progress, and once the release flow is complete, it will change to Completed upon refresh.

note

If you abort the release flow , the status will be updated to Aborted.

Errors and Warnings

• The following error occurs if you do not have network connectivity. Verify your network connectivity to prevent this error.

• The following error occurs if you do not have the required permissions. Verify the permissions assigned to the Backstage user in Release to prevent these errors.

• The following error occurs if the logged-in user does not have permission to access the release plugin in Backstage.

• The following error occurs if you miss or add invalid instance configurations while creating a multi-instance setup.

• The following error occurs if the permission is denied.

Enabling Permissions

The Digital.ai Release 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.

Secure Sidebar Option

To use the permission framework to secure the Digital.ai Release sidebar option, perform the following steps:

• Add permission to your sidebar.

// In packages/app/src/components/Root/Root.tsx file
import { daiReleaseViewPermission } from '@digital-ai/plugin-dai-release-common';
import { RequirePermission } from '@backstage/plugin-permission-react';
-   <SidebarItem icon={ReleaseSvgIcon} to="dai-release" text="Digital.ai Release" />
+   <RequirePermission permission={daiReleaseViewPermission} errorPage={<></>}>
+     <SidebarItem icon={ReleaseSvgIcon} to="dai-release" text="Digital.ai Release" />
+   </RequirePermission>

Secure the dai-release Route

• Add permissions to your dai-release route.

// In packages/app/src/App.tsx
import { daiReleaseViewPermission } from '@digital-ai/plugin-dai-release-common';
-   <Route path="/dai-release" element={<DaiReleasePage />} />
+   <Route path="/dai-release" element={
+     <RequirePermission permission={daiReleaseViewPermission}>
+       <DaiReleasePage/>
+     </RequirePermission>
+     }
+   />

Permission Policy

Here's the example permission policy that you might use to secure the Digital.ai Release plugin:

// In packages/backend/src/plugins/permission.ts
import { daiReleaseViewPermission } from "@digital-ai/plugin-dai-release-common";
class TestPermissionPolicy implements PermissionPolicy {
  async handle(request: PolicyQuery): Promise<PolicyDecision> {
    if (isPermission(request.permission, daiReleaseViewPermission)) {
      if (
        user?.identity.ownershipEntityRefs.includes(
          'group:default/backstage-admins',
        )
      ) {
        return { result: AuthorizeResult.ALLOW };
      }
      return { result: AuthorizeResult.DENY };
    }
    return { result: AuthorizeResult.ALLOW };
  }
}

note

The group "group:default/backstage-admins" is provided as an example and may not exist. You can instead point this to any group available in your catalog.

Support Information

Plugin: @digital-ai/plugin-dai-release-backend

Tested Version:

	Backstage	@backstage/create-app
Legacy Backend System	1.23.0	0.5.11
New Backend system	1.26.0	0.5.14